What are the risks of reversing a data migration?

Technical Q&A

Topic summary

Main issue: After a high-volume data migration was done in summary mode, the poster wants to reverse it, clean up data, and resend in detailed mode, but was warned by support of “major risks” and asks what those risks are.

Current problems: Ongoing sync issues between Shopify and QBDT (QuickBooks Desktop), including unreliable or insufficient syncing. Several transactions, items, and bills repeatedly reappear in sync cycles, flagged either as newly created or as update failures.

Evidence and support history: Multiple Shopify support tickets were closed without resolving the syncing and duplication problems. No technical attachments or code were provided.

Key questions and needs:

  • Clarification on the specific risks of reversing a summary-mode migration and resending in detailed mode.
  • Guidance on addressing repeated creation/update-failed loops and unreliable QBDT sync behavior.

Status: Unresolved and open; the poster is seeking actionable suggestions or risk details before proceeding.

Summarized with AI on January 13. AI used: gpt-5.
1

Due to quantity, my data was migrated in summary mode. I want to reverse the migration, clean up data, and resend in detailed mode. I was told, by support, there is a major risk in doing so. What are these risks?

Insufficient data syncs with QBDT, if it even syncs at all. Several transactions, items, and bills keep repeating in the syncing process, either as created or update failed.

I have a number of closed tickets with Shopify support, all if which have not resolved my issues.

Looking forward to your suggestions.