Separate active operations from the archive
List customers, contacts, open quotes, scheduled moves and relevant reference data. Then identify historical documents and records you need to retrieve. Not every archived document needs to become an editable record in the new software. Agree how the archive will remain accessible and who is responsible for retaining it. Have applicable retention requirements assessed separately; choosing a technical import method does not settle those obligations.
Map fields and document exceptions
Match each source field to its destination. Watch for differences in meaning: a customer number is not a job number, and a preferred date is not a confirmed moving date. Decide how empty fields, duplicate contacts and inconsistent formats should be handled. Ask someone familiar with the records to resolve uncertain cases. An import script can transfer values, but it cannot determine which conflicting customer agreement is correct.
- Source, destination and owner for each data category
- Rules for duplicate and missing information
- Excluded records and their accessible archive location
Validate a small trial import
Select varied examples: a customer with several addresses, a revised quote and a job with attachments. Check relationships and readability as well as record counts. Is the contact linked to the right customer? Can staff still identify the accepted quote? Ask the planner and office staff to try their normal tasks. Record the findings and repeat the trial until the agreed checks pass, rather than treating a completed upload as proof of success.
Agree the cutover and fallback procedure
Decide when entry in the old system stops and how changes made during the transition will be handled. Name the person who approves the final import and explain what happens if an important check fails. Keep a checked backup of the data as it was before the final import. Do not end access to the old product before the agreed validation and archiving are complete. Tell staff clearly which system becomes authoritative once the cutover has happened.
In brief
A controlled migration starts with selection and validation, not the export button. Agree what moves, what stays in the archive and how the team can fall back.