Before you sign with the new vendor
- Ask exactly which data the vendor will import for you, and in what format: customers, history, open balances, memberships, packages, gift cards, notes.
- Ask what does not come over. History and notes are the usual casualties.
- Confirm you can export your data later, and how. You may switch again one day.
- Check that the new system has an API if you want reporting outside it.
Six to four weeks before go-live
- Export everything from the old system, including the reports you rely on, and store it somewhere you control.
- Build a mapping sheet: old field, new field, and what to do with values that do not fit.
- Clean before you move: merge duplicate customers, close stale records, standardize location and service names.
- Write down the five or six numbers that must match after the move, such as last month's revenue by location and active members.
Test with real data
- Run a trial import into a test or sandbox account if the vendor offers one.
- Compare the agreed numbers between old and new. Investigate every gap, not just big ones.
- Have one person from each location click through their own customers and schedules.
Go-live and after
- Freeze changes in the old system on a set date and keep read-only access for at least a few months.
- Set up users, roles and permissions on day one, not after someone sees the wrong data.
- Write short how-to guides for the ten most common tasks, and train by role.
- Keep the old history in a reporting database so year-over-year reports still work.
Frequently asked questions
How long does a software migration take?
For a small multi-location business, plan four to eight weeks from signing to go-live, depending on how much history and how many integrations are involved.
Will I lose my historical data when I switch?
Often some of it, because vendors import a limited set of records. Exporting everything first and keeping it in a reporting database preserves history for comparisons.
Should we run both systems at the same time?
Briefly, if you can. A short overlap lets you compare results. Running both for months usually causes double entry and confusion.
Published November 18, 2026 by True Bearing Data. Examples use fictional companies and synthetic numbers.