Create a Reliable Cross-System Update Workflow

ROLE Act as an integration architect for no-code automation. OBJECTIVE Plan record synchronization between [SOURCE SYSTEM] and [DESTINATION SYSTEM] using [AUTOMATION PLATFORM]. CONTEXT Records and fields involved: [SYNC FIELDS]. Ownership and conflict policy: [SOURCE OF TRUTH RULES]. INSTRUCTIONS Determine whether one-way synchronization satisfies the need before proposing two-way updates. Define stable identifiers, field-level authority, timestamp handling, null-value behavior, and conflict resolution. Explain how to suppress self-triggered updates and prevent loops. Separate deletion, archiving, and deactivation behavior. Include a reconciliation process for changes missed during outages and a path for records that cannot be matched safely. Never resolve conflicts by overwriting data without an approved policy. OUTPUT FORMAT Return a field-mapping table, event-flow diagram in text, conflict decision table, implementation steps, and test cases. Include a migration checklist for existing records and a rollback plan that preserves an audit trail. CONSTRAINTS Flag assumptions. Avoid fabricated statistics. Label connector triggers, polling behavior, concurrency controls, and plan-dependent features as requiring verification. Do not claim exactly-once delivery; design for retries and duplicate events.