Practical trade business guide
How to Move Estimates and Customer Records Into New Software
Migrate customers, locations, estimates, price items, jobs, invoices, and files with mapping, testing, backups, security, and verification.
By Goopuh
How this guide was prepared
Goopuh uses research and AI-assisted tools to organize this guide around a specific reader task. AI assistance is not field experience. We label calculations as examples, link primary or authoritative sources where they are used, welcome corrections, and flag decisions that require a qualified professional or current local requirements.
Quick answer
Move contractor data by preserving an untouched backup, cleaning duplicates, defining the system of record, mapping fields, importing a small test batch, reconciling totals and documents, piloting live jobs, and keeping the old system read-only until the new records are verified. Do not import unnecessary or sensitive data by default.
Tools & Software guideOpen the complete small trade business software guide
Decide what must move and what can remain archived
Prioritize active customers, service locations, open estimates, scheduled jobs, unpaid invoices, current price items, warranties, and recent history that supports daily work. Older closed records may remain in a secure, searchable archive if importing them adds little operational value.
Retention needs vary by record and jurisdiction. Preserve records required for tax, employment, contract, warranty, insurance, licensing, or legal purposes, and obtain professional guidance for the business’s circumstances. Migration is not permission to discard original support.
Create an untouched source backup
Export every available data type and download important documents before changing the source. Record the export date, product, account, file count, record count, and format. Protect the backup from routine editing and store a recoverable copy separately.
Confirm the files open. A completed export notification does not prove that the download contains useful records or attachments.
Clean data before import
Standardize customer names, phone and email formats, billing and service addresses, status values, tax settings, and job identifiers. Merge obvious duplicates carefully while preserving separate properties and contacts. Remove obsolete users and unnecessary sensitive notes.
Do not clean the only original copy. Work from a duplicate and maintain a change log so unexpected results can be traced.
Map every source field to a destination
Create a table showing the old field, sample value, new field, transformation, required status, and owner. Distinguish customer from contact and billing address from service location. Confirm how custom fields, tags, notes, attachments, estimates, invoices, and payments are represented.
| Source field | Destination | Verification |
|---|---|---|
| Customer ID | External or legacy ID | Unique and retained for lookup |
| Service address | Location record | Not merged into billing address |
| Estimate status | Mapped status | Sent, approved, declined, and expired remain distinct |
| Line item tax | Item or document tax setting | Recalculated total matches |
| Attachments | Job or customer documents | File count and access verified |
| Invoice balance | Open receivable | Total agrees with accounting |
Protect personal and business information
Limit migration access to the people performing the work. Use approved transfer methods rather than personal email or unencrypted drives. Remove temporary copies after verification according to a documented process.
The FTC recommends taking stock of personal information, keeping only what the business needs, protecting what is retained, disposing of unnecessary information properly, and planning for incidents. Ask the new provider where data is stored, who can access it, and how incidents are handled.
Import a small representative batch
Test customers with one and several service locations, open and closed estimates, options, taxes, deposits, notes, files, invoices, credits, and duplicate-risk fields. Include imperfect records because those reveal mapping problems.
Review the records in the interface and export them again. A correct screen can still hide missing relationships or inaccessible data.
Reconcile counts, totals, and documents
Compare source and destination counts for customers, locations, estimates, jobs, invoices, and files. Reconcile open estimate value, outstanding invoice balance, deposits, credits, and taxable totals where applicable. Investigate differences rather than accepting a percentage match.
Sample records from the beginning, middle, and end of the export. Open documents and photos. Search by legacy identifiers. Confirm timestamps and approval history when those records matter.
Pilot live work before cutover
Run a controlled set of new jobs from request through estimate, approval, schedule, field work, change, invoice, payment, and job-cost review. Confirm integrations and notifications. Keep the old system available without allowing conflicting edits.
Train users on the new status definitions and correction process. Document where they report missing or incorrect data during the pilot.
Choose and communicate the cutover
Set the date and time after which new records belong in the new system. Assign responsibility for final export, import, reconciliation, integration, access, and user support. Avoid switching during the company’s busiest operational period when possible.
After cutover, make the old system read-only if available. Update forms, bookmarks, automations, email templates, payment links, and accounting procedures that point to the old workflow.
Keep evidence and an exit plan
Retain the source backup, mapping, import files, reconciliation results, issue log, and sign-off. Schedule exports from the new system and test that they remain useful. Document how access will be recovered and how a future migration would begin.
The all-in-one versus specialized tools guide can help prevent unclear ownership after the move.
Free editable tool
Put this guide into practice
Use a practical Goopuh template to capture the details while they are fresh. Email updates are optional.
From template to operating system
Run the workflow in Goopuh Trade Profit OS
Goopuh is building the connected system for estimates, job records, actual costs, customer follow-up, and clearer profit decisions.
Frequently asked questions
Should every historical customer be imported?
Not automatically. Import records that support active work, service history, warranties, receivables, compliance, or customer service. Preserve other required records in a secure archive.
How can duplicate customers be prevented?
Define matching rules using stable fields, preserve legacy IDs, separate contacts from locations, test duplicates, and review ambiguous matches manually.
When can the old software be cancelled?
After required data and documents are backed up, the new system is reconciled, live workflows pass, integrations work, and the business understands how long old access and exports remain available.
What is migration reconciliation?
It is the comparison of source and destination record counts, balances, totals, statuses, documents, and sample details to prove that the migration is complete enough for its purpose.