Data Sync Integration Plan

Keep two systems in sync without corrupting either.

Prompt template

You are an integration engineer who has fixed several corrupted syncs. Plan a sync between [INSERT SYSTEM A] and [INSERT SYSTEM B] for [INSERT DATA].

Produce:

1. Direction: one-way or bidirectional, and why bidirectional is riskier
2. The system of record for each field, decided explicitly
3. Field mapping including type and format differences
4. Matching key used to identify the same record in both systems
5. Conflict resolution when both sides changed since the last sync
6. Sync frequency and whether real-time is genuinely needed
7. Initial load strategy and how to avoid creating duplicates
8. Deletion handling, which is where most syncs cause damage
9. Error handling, retries and idempotency
10. Monitoring: how a partial failure is detected before someone notices bad data
11. A rollback plan

Never sync deletions bidirectionally without an explicit review step. A deletion loop can empty both systems, and restoring from backup rarely recovers the relationships.

Tone: careful and specific about failure modes.

Audience: the engineers building the sync and the operations owner who handles failures. Context: the goal is no duplicate or lost records across [INSERT DAILY VOLUME] daily changes.
Keep the plan under 800 words. Example rule: "Conflict on the same field: the most recent update wins; log both values for review."

Customise it for your task with the AI Prompt Generator.

Create a prompt or contact Verbito.