Switching HVAC software without losing the useful history.
A migration is an operating decision, not a data upload. Start with a small, reconcilable trial.
Export a representative record set, decide which system owns each record during the trial, prove a real job path, and reconcile the results before asking the whole shop to change.
Start by naming what must survive
Commercial HVAC records are uneven. Customer and site lists may be clean while unit identity, photos, open repairs, agreement obligations, and old reports live in different places. Do not promise a complete history migration before seeing the exports. First make an inventory of what exists and what the team actually needs on the next service call.
A practical trial sequence
- Export a representative sample. Include customers, sites, contacts, equipment, active agreements, recent reports, photos or attachments, open quotes, work in progress, and the accounting records needed to reconcile.
- Map the records. Identify stable IDs, duplicate risks, unit-location mismatches, missing dates, and documents that cannot be imported cleanly. Keep a source copy and name the owner for each exception.
- Choose where each record lives. While testing, define where scheduling, field notes, reports, quotes, invoices, payments, and customer communication are authoritative. Avoid double entry that no one has agreed to reconcile.
- Run two representative jobs. Use one PM visit with several units and one reactive call with an outstanding repair. Test field capture, office review, report output, quote follow-up, and accounting handoff.
- Reconcile before expanding. Compare counts, key customer and unit data, report outputs, open work, and invoice totals. Resolve discrepancies while the sample is small.
Questions that expose risk early
Can you export your data again after the trial? What attachments remain linked to equipment? How are duplicates handled? What happens when a technician records work offline? What is the correction path if an imported unit is linked to the wrong site? Who approves the cutover and who can stop it? These are operating questions, not implementation trivia.
Keep the claim honest
No software page can certify a migration from a generic description of your data. Imports depend on the source system, export permissions, data quality, and the agreed target model. A vendor should show the planned mapping, the limits, the reconciliation method, and the recovery owner before a production switch.
Use the comparison test script to decide whether a trial is worthwhile. If reports are the immediate bottleneck, try the free service-report builder and read the closeout guide.
Try it on a service call.
Build a report now, or bring a redacted work order to a walkthrough of BoltWright.
Build a free report Book a walkthrough