Data migration and cutover
Plan ownership, mapping, deduplication, rehearsal and rollback before moving business records.
Author：WeTech technical team · Updated： (Hong Kong time (GMT+8))
A migration includes inventory, cleaning rules, trial runs, reconciliation, cutover and retirement. Imported row counts do not prove that relationships, amounts, attachments or permissions are correct. Business owners must verify key records and agree a workable recovery path.
When to use this guide
For CRM replacement, order-system changes, accounting connections or moving spreadsheets into internal applications.
Migration acceptance checklist
| Stage | Decision | Acceptance evidence |
|---|---|---|
| Inventory | Master data, history and exclusions | Source and owner register |
| Mapping and cleaning | Fields, codes, merge rules | Transformation table and exceptions |
| Trial and reconciliation | Counts, relationships, totals, samples | Differences and corrections signed off |
| Cutover | Freeze, deltas and recovery | Cutover log and user confirmation |
Deduplicate without losing history
Distinguish duplicate customers, repeated transactions and separate entities with similar names. Preserve original identifiers and merge mappings so historical activity remains traceable. Escalate ambiguous matches rather than merging records solely because names or telephone numbers resemble one another.
Rehearse failure and recovery
Trial the migration in an isolated environment, checking Chinese text, dates, currencies, attachments and permissions. Define the write freeze, final delta capture and stop authority. Recovery must address transactions created after cutover as well as restoring an earlier backup.
Verify relationships after import
Beyond totals, sample business chains such as customer-to-order and order-to-attachment, explaining expected differences. After business sign-off, apply retention rules to legacy copies, test exports and temporary accounts. Avoid leaving migration files in publicly accessible locations.
Illustrative scenario
Hypothetical example: preserve source IDs from two customer spreadsheets, review conflicting contacts and trial one team in the new CRM. Keep the legacy system available until reconciliation and cutover conditions are satisfied.
Frequently asked questions
Is a successful import sufficient?
No. Verify relationships, fields, permissions, attachments and user workflows.
Must every historical record move?
Decide by use, retention and retrieval needs; active and archived records can be separated.
Can we test with production records?
Confirm authorisation, access and deletion arrangements; prefer suitable de-identified test data.
Brand and public case scope
WeTech Consulting, also called WeTech or WeTech AI HK, provides AI and IT consulting in Hong Kong. WeProperty HK and WeCredit HK are self-developed products. Their cases support the observable features listed: property, estate and transaction-reference entry points for WeProperty; submission, review and public-data masking for WeCredit. WeCredit is not a TU credit-rating service or a final determination of facts.
WeProperty HK · WeCredit HK (case studies in Traditional Chinese)
Reference sources
- Microsoft: Integrate data into Dataverse
- Microsoft Learn: Detect duplicate data
- PCPD：Artificial Intelligence: Model Personal Data Protection Framework
Official documents support the technical, risk and measurement concepts. Checklists, estimation methods and illustrative scenarios are WeTech planning recommendations, not official prices or client results. Check the supplier’s current plan and terms. Sources reviewed: (GMT+8)
Related guides
Discuss your project
Share your workflow, systems and goals. We will review scope before discussing deliverables, acceptance and a quotation.
Request an initial consultationExplore this service