Import and export customer data

I need the customer database moved into our new store and the old store cleaned up. Export all customers with emails, phone numbers, tags, and account creation dates from the legacy store, import them into the new live store without creating duplicate accounts, and then remove inactive test accounts older than 24 months. Do the export, run a duplicate-check, import only unique records, and produce a one-page CSV summary of how many imported, skipped as duplicates, and deleted. Deadline Friday EOD.

Before I hand this customer CSV to the operations team, make approving it trivial. Show total customers and new-import revenue potential at the top, highlight any customers with multiple email addresses or mismatched phone numbers, surface tags that look like test accounts, and flag rows that will create duplicates. Suggest quick rules to resolve the five riskiest uncertain rows so a reviewer can sign off in under five minutes.

I just exported customers and found dozens of duplicate emails with conflicting phone numbers and tags. The migration goes live Monday, operations expects a clean import, and I cannot reach the head of CX to confirm merge rules. I’m worried merging will collapse distinct accounts or importing as-is will create fragmented histories. What’s the most pragmatic safe move now, and how should I explain the risk to operations in one sentence?

Over the last three migrations we spend the most time chasing duplicated customer records and fixing tags after import. It costs support hours and confuses marketing segmentation. What one habit or checklist change will stop this recurring firefight so future imports land cleanly every time? Describe the change and the first two implementation steps.