Switch without losing repair history

The short answer

To switch collision shop management systems safely:

1. Inventory every place the shop stores operational records.
2. Decide which system remains the source for closed history, accounting, estimates, photos, and payments.
3. Export and verify a sample before changing anything.
4. Configure the new shop before moving live work.
5. Bring over the customer records and active repair orders the team needs now.
6. Run a small pilot, then choose one cutover date.
7. Keep read-only access or a verified archive of the old system for the required retention period.

The goal is not to put every old screen into a new screen. The goal is to make sure the shop can find the old record when it needs it and run every current repair from one agreed process.

Start by deciding what the word "history" means

In a body shop, repair history is spread across more than one system. A closed file may include:

• Customer and vehicle details
• Repair orders and line items
• Original estimates and supplements
• Photos, scans, signed forms, and releases
• Parts orders, receipts, returns, and credits
• Customer and adjuster messages
• Labor entries and production events
• Invoices, payments, and accounting entries
• Audit history showing who changed what

Do not assume one export contains all of it. A simple source-of-truth chart is enough:

This chart prevents the most common migration mistake: moving data simply because it exists, without deciding how the shop will use it.

You may not need to move closed repair orders

If estimators will continue writing in the same estimating system, old estimate and supplement history can stay there. Your accounting history can stay in the accounting system. The new shop-management system can begin with active work and become the complete operational record going forward.

That is often cleaner than importing a large archive with duplicate customers, old statuses, inconsistent insurer names, and attachments that no one has opened in years.

Before canceling an old subscription or changing permissions, confirm:

• How long read-only access remains available
• Whether access depends on an active paid account
• Which exports include documents and full-resolution images
• Whether the exported files preserve dates, repair-order numbers, and customer or vehicle relationships
• How the shop will search the archive later
• Who is responsible for retaining it

Record-retention periods depend on the record, the shop's location, insurer or DRP agreements, tax requirements, and any active dispute. The IRS says the proper retention period depends on the action, expense, or event a record supports, and advises businesses to check whether insurers or creditors require longer retention. Treat retention as a business and legal decision, not a software default. See the IRS record-retention guidance.

A practical 10-step cutover plan

1. Name one switch owner

One person should own the checklist, dates, vendor questions, and final sign-off. Other people can handle their areas, but one person must answer, "Are we ready to cut over?"

2. Inventory every working system

Include more than the old management system. List the estimating platform, accounting, payment processor, texting service, photo storage, shared drives, spreadsheets, calendars, booking forms, and any paper logs the floor still uses.

Record the account owner, admin login, contract end date, export options, and records the shop relies on.

3. Separate active work from closed history

Create three buckets:

• Move now: Active repair orders, current estimates and supplements, open parts issues, pending approvals, balances, promised dates, and live customer conversations.
• Import if useful: Current customer and vehicle list, insurer contacts, vendors, staff, stages, templates, and shop hours.
• Keep accessible: Closed repairs, old estimates, settled accounting periods, completed payment records, and old documents.

Do not let a perfect historical migration delay a useful operational switch.

4. Export a sample and inspect it

Before the full export, choose five records that represent real shop complexity:

• A normal completed repair
• A supplement-heavy repair
• A repair with many photos and documents
• A fleet or commercial customer
• A total loss or another unusual closeout

Open the exported data and files. Check names, VINs, repair-order numbers, dates, totals, notes, photo quality, and attachments. Make sure the records can be understood without the old screen around them.

The Federal Trade Commission recommends putting vendor expectations in writing, including how they use, retain, and delete data. See the FTC's small-business vendor security guidance.

5. Make a protected archive

Keep the verified export separate from the computer used for daily work. CISA recommends maintaining offline, encrypted backups of critical data and testing that they can be restored. A backup that no one has opened is only a promise. See the CISA ransomware guide.

For a shop migration, "test the restore" can be simple: open a representative set of records and images from the archive on a different computer, then document where the archive lives and who can access it.

6. Clean the data worth importing

Customer imports are where old mess often becomes new mess. Before importing, remove obvious duplicates, fix broken phone numbers, standardize company or fleet names, and decide which record wins when the same vehicle appears twice.

Do not spend weeks perfecting unused historical contacts. Clean the people and vehicles the shop expects to work with again.

7. Configure the shop before the first live RO

Set up:

• Shop name, address, hours, and time zone
• Production stages and handoff rules
• Team members, roles, and shared-device access
• Capacity and scheduling rules
• Message templates and customer consent process
• Vendors, insurers, labor settings, and payment options
• Estimating and accounting connections

Then walk one test repair from arrival through delivery. A test record exposes missing stages and permissions faster than a conference-room discussion.

8. Pilot with a small group

Choose one estimator or CSR, one production lead, one parts user, and one technician. Have them create and find a customer, connect an estimate, assign work, record a parts event, send a customer update, and confirm that managers see the same status.

9. Pick one cutover rule

A clean rule might be: "All vehicles already on site Friday are entered in the new system. Closed work stays in the old system. New Monday arrivals start in the new system." Write it down. Two live records create two answers.

10. Validate the first week

At the end of each day, check:

• Every on-site vehicle is on the new board
• Promised dates and owners are assigned
• Current estimates and supplements are attached to the right RO
• Parts holds and backorders are visible
• Customer replies are reaching the team
• Balances and payments agree with the accounting process
• No one is keeping a private shadow spreadsheet

Fix the process while the number of records is still small.

Questions to ask before signing

Use this checklist during the buying process:

• What data can we import, and in which formats?
• Can we start with active work instead of all historical repair orders?
• Can we import customers without importing closed jobs?
• How are duplicates identified?
• What happens to documents and full-resolution images?
• How do CCC ONE, Mitchell, Audatex, or other estimate files enter the system?
• Which connections require third-party approval?
• Can technicians sign in without a company email?
• How long does a typical shop setup take?
• Who configures stages, templates, roles, capacity, and payments?
• What support is included during onboarding?
• Can we export our data, documents, and images without opening a support ticket?
• What happens to our data when the subscription ends?

The AutoHound approach

AutoHound does not require a shop to recreate years of closed repairs. Estimators can keep old repair history in the estimating system they already use. The shop can bring current work into AutoHound, create the active repair orders it needs, and import current estimates or supplements.

The customer book can be imported if the front office wants it. Going forward, the connected AutoHound RO holds production, parts, documents, messages, payments, and reporting around the repair.

AutoHound also gives each employee access by phone number, email address, or both, which helps shops that do not issue work email to every technician. See the full Switching to AutoHound process, review estimating-system connections, and see how the connected repair order works.

Final cutover checklist

Before declaring the switch complete, confirm:

• The old-system export has been opened and verified
• Retention requirements have been reviewed
• Closed history remains searchable
• Active ROs have a clear owner and current stage
• Current estimates and supplements are attached
• Parts holds, promised dates, and balances are correct
• Staff roles and logins work on office and floor devices
• Customer messaging and consent settings are active
• Accounting and payment workflows have been tested
• The team knows the single cutover rule
• A manager has reviewed the first week of work

A safe switch is not a giant data dump. It is a controlled handoff. Preserve access to the records the shop must retain, move the work the team must act on, and make the new system the one place everyone trusts from the cutover date forward.