Move Garage Customer Spreadsheets into Pistonlog

A garage customer spreadsheet import is an opportunity to make your records easier to use. Moving every row unchanged can also carry years of duplicate names, outdated vehicle links and uncertain contact details into the new system.

Pistonlog provides a combined customer-and-vehicle CSV import. Use its supplied template and test a small sample first. Here is how to prepare the information before uploading it.

Keep the original export untouched

Save a working copy for preparation and keep the source export separately. Record which system or spreadsheet produced it and when. If a mapping question appears later, you can return to the source rather than trying to reverse several rounds of edits.

List the columns you currently have and decide where each belongs in the Pistonlog template. Do not squeeze an unrelated note into a field just because the original column has nowhere to go. Keep information outside the import scope in an appropriate separate record.

Use the app's actual template

Download the template from Pistonlog's import page and retain its headings. The documented importer expects its own format, including a template version and customer reference.

The import uses one row per customer-and-vehicle pair. For a customer with several vehicles, the repeated customer reference and details must agree. A customer without a vehicle can also be included. The CSV import guide lists the fields and limits.

This is a customer-and-vehicle import. Historical invoices, jobcards, inspections and payments need their own retention or migration plan.

Check relationships before duplicates

Start by confirming which customer currently belongs with each vehicle. Similar names do not prove two records are the same person, and an old registration link does not prove current ownership.

Then review likely duplicates using several details together. Look at contact information and the original record before deciding what to keep. Avoid changing a real customer's details simply to make an import validation message disappear.

Pistonlog documents customer matching by email or by name and phone, and vehicle matching by registration. Understand those rules before uploading records that share details.

Make contact preferences explicit

Review email and SMS preference fields rather than leaving them to chance. The documented importer treats blank contact-preference fields as true, so enter the intended values explicitly after checking your source records.

A technical default is not evidence that a customer agreed to receive a particular message. If your source preferences are unclear, resolve the question before using imported details for messaging.

Review the preview and sample results

Upload a small representative batch and read the preview. Resolve errors in the working file and check the expected customer and vehicle links before confirming the import.

After import, open sample records. Check business customers, customers with multiple vehicles and any records expected to match existing entries. Verify the outcome, then move on to the remaining batches within the documented limits.

The import guide describes a limited undo option, but preparing and checking the records is still the safer workflow. Do not use undo as a substitute for reviewing the preview.

Moving into Pistonlog customer and vehicle records gives the information a home alongside workshop jobs. Ask us about your spreadsheet if you need to confirm the mapping before starting.