HVAC Software Migration Checklist
Switching field service software is a project, not a weekend install. Use this checklist to move customers, equipment, open work, and memberships without losing history or stalling the trucks.
1. Inventory what you have before you touch exports
Pull counts from the current system: customers, properties/locations, equipment records, open estimates and invoices, active service agreements/memberships, jobs in the last 24 months, and every integration (accounting, payments, phone/SMS, financing). Write down who owns the project and a target go-live date. Most shops need roughly two to four weeks of focused work — rushing creates import messes; dragging it out creates dual-system confusion.
2. Decide what migrates vs. what archives
Must-move: customer contacts, service addresses, equipment (make/model/serial/age), open estimates and invoices, active memberships, and recent job history techs still reference. Nice-to-archive externally: old completed jobs beyond two to three years, stale notes, and unused templates. Open work orders often migrate cleaner when you complete or close what you can before cutover and re-enter the remaining active jobs by hand in the new system.
3. Export everything — then verify the files
Export customers, properties, equipment, jobs, invoices, and agreements (usually CSV). Download PDFs of active proposals and membership contracts if the new platform will not recreate them perfectly. Store copies in two places. Open the files and spot-check rows before you cancel anything — a corrupt export is the same as no backup. Ask both vendors in writing what they support for import templates, field mapping, and migration help.
4. Clean and map before the big import
Deduplicate by phone, email, or service address. Fix blank emails, inconsistent address formats, and equipment sitting on the wrong property. Map old fields to new ones and note custom fields that need equivalents. Import a small sample (tens of customers and a handful of properties/equipment) first. Confirm counts, links (customer → property → equipment), and formatting before loading the full set.
5. Prioritize go-live scope — do not boil the ocean
A proven order: (1) customer and location database, (2) dispatch plus estimate-to-invoice workflow, (3) price book, (4) core integrations such as QuickBooks or payments, (5) memberships, marketing, and advanced reporting. It is better to run with incomplete advanced features for 30–60 days than to delay cutover while every module is perfect. Confirm accounting sync, payment processors, and SMS/phone before day one.
6. Train by role with real HVAC scenarios
Train CSRs, dispatchers, and technicians separately on the jobs they actually run — for example a no-cool emergency and a membership tune-up. First sessions cover daily work only: booking, dispatch, job notes, invoices, and payments. Defer advanced features. Name one internal champion per crew so questions do not all escalate to the owner. Pilot with one adaptable crew for one to two weeks before company-wide rollout.
7. Cut over on a calm day and keep a rollback path
Prefer early week or a lower-demand HVAC window — not peak heat or a holiday backlog. Run parallel for about one to two weeks when possible: new jobs in the new system, old system available for history. After hard cutover, keep the old platform read-only for 30–90 days (some shops keep it longer). First-week monitors: customer/property counts, membership renewals firing, invoice totals vs. the prior week, and tech mobile adoption. Have vendor support contacts and a written rollback trigger if dispatch or invoicing breaks.
Pre-go-live sign-off list
Customer contacts transferred and spot-checked. Properties linked to the right customers. Equipment on the right properties. Open estimates/invoices handled. Active service agreements live or scheduled. Recurring maintenance on the calendar. Price book usable for the most common residential calls. Accounting/payments smoke-tested. Staff trained by role. Old-system export archived. Affiliate and vendor CTAs in this directory stay pending until real programs are approved — always Check vendor for current migration assistance and pricing.