Plumbing Software Migration Checklist: Preserve the Business Record

Define what must keep working

List the business activities that cannot lose continuity: contacting customers, finding property history, quoting approved work, seeing scheduled jobs, sending accurate invoices, and explaining payment balances.

That list should drive the migration scope. A customer import alone may be enough for a limited fresh start, but it is not equivalent to moving the complete business history. Make the choice explicit.

Use the migration checklist

MIGRATION CONTROL LIST
[ ] Source systems and responsible owners identified
[ ] Customers, properties, estimates, jobs and invoices inventoried
[ ] Payment evidence and allocations inventoried
[ ] Pricebook items, notes and attachments inventoried
[ ] Original exports preserved unchanged
[ ] Export dates, filters and scope recorded
[ ] Source IDs and relationship fields retained
[ ] Field mapping and status meaning documented
[ ] Unsupported or ambiguous fields listed
[ ] Small representative import tested
[ ] Duplicate and retry behavior checked
[ ] Record counts and financial controls reconciled
[ ] Active jobs and next actions verified with the team
[ ] Cutover point and new-work handling agreed
[ ] Archive/access arrangements verified
[ ] Final exceptions and owners documented

Treat an unchecked item as a question to resolve, not something to hide before declaring the migration finished.

Map relationships before cosmetic cleanup

A correctly capitalized customer name is less important than preserving which jobs and invoices belong to that customer. Keep stable identifiers and the links among entities.

Do not merge records only because names or amounts match. A property manager can have several properties, and two invoices can have the same total. Use the actual source relationships where available.

Preserve unmapped information in a documented archive or supported metadata process. Do not silently drop a field simply because the destination does not have an obvious equivalent.

Test the cases most likely to fail

Include a customer with multiple properties, a long note, an inactive item, an open estimate, a completed-but-uninvoiced job, a partial payment, and a refund or adjustment where relevant.

Check whether the destination creates, updates, or rejects an existing record on a retry. Rerunning an import without understanding that behavior can create duplicates.

This checklist is vendor-neutral. Verify GoPlumber's current import support for each entity rather than assuming every source export can become a native record automatically.

Reconcile meaning as well as totals

An imported invoice total, outstanding balance, and payment total measure different things. Do not force them to match by inventing payment rows or changing statuses without evidence.

For a fictional example, a $1,000 invoice with a verified $300 payment should preserve both amounts and the $700 remaining balance, subject to any actual adjustments. Importing only $700 as the original invoice amount loses part of the history.

Have an accountant review financial classifications and any effects on posted records.

Control the cutover

Choose how work created after the export date will be handled. Options depend on the systems and business process, but the decision must prevent active jobs from being left in two inconsistent places.

Do not cancel access to the source before checking your contractual, retention, and data-access requirements. Keep the records needed to operate and answer future customer questions.

A useful migration sign-off names what moved, what was tested, what remains unavailable, and who owns each exception. “The upload completed” is only one small part of that conclusion.