Switching Software: How to Migrate Without Losing Data

You have outgrown your current setup, but the thought of moving everything across fills you with dread. What if a customer's history disappears? What if half-finished quotes vanish? Fear of losing data is the single biggest reason trade businesses stay stuck on software they hate. It does not have to be that way.

A migration done properly is dull, predictable and reversible. This guide walks you through exactly how to switch software without losing a thing.

Why Switching Feels Risky (and Why It Usually Is Not)

Your business data is years of customer records, job history, certificates and unpaid invoices. Losing any of it would be a nightmare, so caution is sensible. The risk, though, comes almost entirely from rushing or skipping steps, not from the move itself.

The good news: almost every modern system stores your information in standard formats you can export. As long as you have a copy of your data before you start, a migration can always be undone. You are never burning the boat until you have proven the new one floats.

Step One: Take Stock of What You Actually Have

Before exporting anything, list what lives in your current system. Most trade businesses have more than they realise:

• Customer and site details (names, addresses, phone numbers, emails)
• Job and project history, including notes and photos
• Quotes and estimates, both won and pending
• Invoices and payment records, especially anything unpaid
• Certificates and compliance documents (EICRs, gas safety records, RAMS)
• Recurring jobs and service reminders
• Supplier and price-list information

Mark which of these you genuinely need to carry over. You rarely need ten years of completed jobs in the new system, but you absolutely need every open quote, unpaid invoice and live customer. Be honest about what is "nice to have" versus business-critical.

Step Two: Export and Back Up Everything First

Never start a migration without a full export sitting safely on your own computer. This is your safety net.

Most systems let you export to CSV (a simple spreadsheet format that opens in Excel or Google Sheets) or PDF for documents. Pull out:

1. A CSV of all customers and sites.
2. A CSV of jobs, quotes and invoices.
3. PDF copies of every certificate and signed document.
4. Any photos attached to jobs, downloaded in bulk if the system allows.

Store these in a clearly labelled folder, and keep a second copy somewhere else, such as cloud storage. If your current provider offers a one-click "export all my data" option, use it. If you cannot find an export route, contact their support before you cancel anything.

Tip: Do your export before you give notice to cancel. Some providers lock you out the moment your subscription ends, and getting data back afterwards can be slow or impossible.

Step Three: Clean the Data Before It Moves

A migration is the perfect moment for a spring clean. Importing junk just moves the mess to a tidier-looking home.

Open your customer CSV and scan for the usual problems:

• Duplicate customers (the same person entered twice)
• Old test entries or training-day rubbish
• Missing postcodes or phone numbers
• Inconsistent formatting (mix of "St" and "Street", capitals everywhere)

Fix the obvious issues in the spreadsheet first. It is far quicker to tidy a column in Excel than to fix records one by one later. Smaller, cleaner data also imports faster and with fewer errors. This is also a good time to think about how you will store certificates and stay audit-ready in the new system, so nothing important slips through.

Step Four: Import in the Right Order

Data has dependencies. A job belongs to a customer; an invoice belongs to a job. Import things out of order and the links break, leaving orphaned records.

Follow this sequence:

1. Customers and sites first. Everything else hangs off these.
2. Jobs and historical projects next, linked to the customers you just added.
3. Quotes and invoices, attached to the right jobs.
4. Certificates and documents last, filed against the relevant customer or job.

Most good job-management platforms provide an import wizard that maps your spreadsheet columns to the right fields. Take your time matching them up. A column mapped wrongly (phone number landing in the email field, say) is the most common migration mistake, and it is easily avoided by checking the preview before you commit.

If your new provider offers a guided import or migration help, take it. A system like Gaffer can pull customers, jobs and outstanding invoices across so you are not retyping years of records by hand.

Step Five: Run Both Systems in Parallel

Do not flip the switch overnight. The safest cutover is a short overlap where both systems run side by side.

For one to two weeks:

• Enter all new jobs and quotes into the new system only.
• Keep the old system live but read-only in your mind, used purely to check anything looks wrong.
• Chase any open invoices from wherever they were raised, so nothing falls through the gap.

This overlap lets you catch missing data while you can still go back and grab it. Once you are confident every live job, customer and unpaid invoice is correctly in the new system, you can retire the old one. Pay special attention to outstanding money, because there is no quicker way to spot a migration gap than an invoice you forgot to chase. If late payment is already a struggle, sort your process for getting paid faster as part of the move.

Step Six: Check, Then Cancel

Before you cancel the old subscription, run a final spot-check:

• Pick ten random customers and confirm their details and history carried over.
• Confirm every unpaid invoice exists and shows the right balance.
• Open a few certificates to check the files actually downloaded, not just the records.
• Make sure recurring jobs and service reminders are set up again, as these rarely transfer automatically.

Only when you are happy should you cancel. Even then, keep your exported backup folder for at least a year. It costs nothing to keep and saves you completely if a question comes up about an old job.

FAQs

Will I lose data when switching job-management software?

Not if you export and back up everything before you start. As long as you have your own copy of customers, jobs, invoices and certificates on your computer, any migration can be checked and corrected without losing a thing.

How long does it take to migrate to new trade software?

For a small trade business, the actual import often takes a day or two, with a one-to-two-week parallel-running period to be safe. The bigger the history and the messier the data, the longer the clean-up beforehand takes.

Can I import customers and invoices from a spreadsheet?

Yes. Most job-management systems accept CSV imports and provide a wizard to map your spreadsheet columns to the right fields. Customers usually import first, then jobs, then invoices, so the links between them stay intact.

Should I keep my old software running during the switch?

Yes, for a short overlap. Running both in parallel for a week or two lets you spot anything missing while you can still retrieve it, then cancel the old subscription once everything checks out.