On Monday morning, a customer rings about the noise you looked at last winter. You need to find the old job card, see which part you fitted and check what the customer still owes. A successful software switch means you can answer that call while the rest of the team gets on with the day.

Protect the records you need, prove that a small import works, and plan which diary will take new bookings at the point you switch. Here’s a way to do that without turning a normal week at the workshop into a data project that never ends.
Ask the people at the counter and on the ramp what they look up during a normal day. You’ll probably hear about customer names, registrations, job history and outstanding invoices. Keep asking. Where is approval for a repair recorded? Who can see inspection photos? How do you know that a service reminder has already been sent? A list of records is useful. A list of questions your team needs to answer tells you which links and attachments matter.
| Records | What staff need to find |
|---|---|
| Customers and vehicles | Who owns each vehicle, which fleet it belongs to, and how to contact the correct person |
| Upcoming bookings | Date, time, status, length, bay or technician, and any loan car or collection arrangement |
| Quotes, job cards and inspections | What was offered, what the customer approved, work carried out and the photos or notes that support it |
| Invoices and payments | Original references, totals, VAT, credits, part payments and the outstanding balance |
| MOT and service dates | The right vehicle, due date and any reminder already sent |
| Customer preferences | Contact preferences, relevant marketing permissions and records of opt-outs |
Decide which of those records need to move into the new system and which you can keep in a searchable, controlled archive. A seven-year-old closed job might only need to be found occasionally. Tomorrow’s bookings and last week’s unpaid invoices need to work during a busy morning.
Still comparing systems? See our comparison of seven UK garage management systems.
Get an example of each export from the old supplier. Ask whether it includes the full record or only a summary, what identifies a customer, and how the vehicle, invoice and payment link together. Check whether attachments come in the same export or a separate download. An invoice PDF is useful evidence of the original document, but its existence says little about whether your new system can bring in the payment and outstanding balance as structured data.
Ask the new supplier to confirm its import fields and what happens to records it can’t match. As a published example, Garage Invoice documents separate imports for customers, vehicles, appointments, job cards, quotes and invoices. Its invoice import uses a row per line item and can include payment information. There’s also a separate payment import for existing invoices, so check which route your migration will use to avoid recording a payment twice. Its FAQ also describes CSV export and bulk PDF downloads for supported documents. Export and import coverage can differ, so check each record type with your provider before you choose the switching date.
Read more: Garage Invoice data import guide · Garage Invoice FAQ
Keep a short list with the export name, who has access, what it contains and when you tested opening it. Agree when old-system access ends. A supplier may close the normal workspace before an administrator’s export window ends, and either date can catch you out if you only find it on the day.

Save the untouched exports and original documents in protected storage that the people doing the move can access. Make a working copy for fixing columns and matching records. Test that you can open both the archive and the attachment folders. The UK government’s 2025/26 Cyber Security Breaches Survey found that 74% of businesses reported securely backing up data via a cloud service, based on responses from 2,112 UK businesses. For a software move, the practical question is whether your own backup contains the exact records and attachments you can restore.
Sources: UK Cyber Security Breaches Survey 2025/26 · NCSC small organisation backup guidance
Check easy-to-miss details first. Phone numbers can lose their first zero when spreadsheets treat them as numbers. A date such as 04/05/2026 can be interpreted two ways. A registration may appear with or without a space and a customer might have changed plates. Use explicit date formats accepted by the new system, treat contact and identification fields as text when appropriate, and keep original IDs in the working files so you can trace a record back.
Source: Microsoft guidance on keeping leading zeros in Excel
Avoid merging people just because they share an email or a surname. A husband and wife might use the same inbox for different vehicles. A fleet might have one accounts email and six drivers. Check those exceptions against the source before importing. Ask who should approve corrections and keep a short log of what was changed.
Plan retention with the accountant and whoever looks after personal data. HMRC generally requires VAT records to be kept for at least six years. If Making Tax Digital for VAT applies, plan how you’ll keep the required digital records and maintain any digital links between systems. Retention periods for personal data depend on what you need the data for. Document the purpose and remove temporary exports once you’ve finished with them. Where a provider acts as your processor, check the contract for the return or deletion of personal data at the end of the service.
Sources: HMRC VAT records guidance · ICO storage limitation guidance · ICO processor contract guidance
A test batch of ten clean customers can look fine while a fleet, a number-plate change and a part-paid invoice all go wrong. Include known exceptions. In Garage Invoice, the documented starting order is customers, vehicles, then documents such as invoices and job cards so the import can link them. Check the order for the software you’re moving to. Use a test environment if your provider offers one. If not, start with a small file of a few rows. Either way, stop test records from triggering live messages or accounting exports.
Read more: Garage Invoice import mapping and review guidance
Before the test, the old system shows 20 customers, 26 vehicles and eight open invoices with £3,260 due after payments and credits. The new system shows the same invoice count and £3,510 due. Checking by invoice number reveals that one £250 part payment did not come across. Find out why, correct the test and compare the balances again. A matching number of invoices can hide a wrong balance.
Have the team test a few questions without the migration lead helping them. Can they find an invoice by registration? Can they open an old inspection photo? Does the payment show against the correct invoice? Can they see the collection address for tomorrow? Check the answers against the source and note anything that will need a separate archive lookup or manual handover.

Choose a quiet window with someone available from the software team and someone from your workshop who can verify the books. Decide when staff should stop adding or changing appointments in the old diary. If customers can book online, change the link at the agreed point and make a test booking. Assign one person to capture any bookings, invoices or payments that arrive after the first export so they appear once in the new system.
Before you let the whole team in, check the next week’s diary, the open invoice balances and a sample of linked job histories. Confirm which system sends reminders, welcome emails, overdue notices and information to your accounting software. Run one controlled test of each integration before relying on it. Keep a list of what would stop the switch. An unexplained balance, missing appointments for tomorrow or customer messages firing from both systems are good reasons to pause and fix the issue.
Keep authorised read-only access or a tested archive long enough to reconcile the move and support records you still need to retain. Agree what the team does if a key check fails. If you have to return to the old system temporarily, make a list of changes recorded after the switch and reconcile them before someone enters them twice.
When the next customer rings about last winter’s repair, try the search yourself. A clean migration means being able to find the agreed work, the fitted part and the balance in whichever approved place you chose to keep them. Start by checking which records your supplier can bring across.
Read more: Garage Invoice data import guide