IMPORT & EXPORT

Your data should be understandable and portable.

Moving customers, service addresses, job history, and equipment records is easier when the files are clean and the mapping rules are clear.

Something to build on · 01

Start by understanding the source

A CSV export may contain duplicate contacts, old billing addresses, mixed customer/property fields, and dates in different formats. Review the source before importing. Cleaning up bad records in a spreadsheet can be easier than repairing thousands of mistakes afterward.

Something to build on · 02

Map each field intentionally

Decide which source column becomes customer name, property address, contact phone, equipment identifier, appointment date, and job status. Preserve IDs where appropriate and document what happens when required information is missing.

Something to build on · 03

Run a small trial

Import a representative sample that includes multiple properties, repeat customers, old equipment, open jobs, and a few bad records. Check what arrived, what was rejected, and whether staff can find the expected history.

Something to build on · 04

Plan for export before you need it

Ask vendors what can leave the system: customers, properties, work orders, photos, invoices, payments, and audit history. Export format, timing, permissions, and retention are part of a good buying decision.

Example to try: A client has one billing account with three service addresses. The import should not silently flatten all three into one location.

Something to build on · 05

A practical checklist

  • Preserve customer-to-property-to-equipment relationships through sample import.
  • Flag duplicate phone numbers rather than treating them as automatic duplicate customers.
  • Check invalid rows, timezone conversions and blank-field behavior.
  • Request a representative export of every dataset needed for business continuity.

Good questions

What else would
you like to know?

Do you support Excel files?

Import and export formats have to be verified for each dataset; CSV is a common starting point.

Will migration remove duplicates?

Deduplication is a separate data-quality process and should never silently merge customers without reviewed rules.

Can I export everything when leaving?

Data portability and contract terms require a documented supported export inventory.

Your next chapter

Start with one job.
See the whole picture.

Follow an illustrated service call, from the first request to closeout.

See how it works