Switching business software: a clean cut-over checklist

A clean switch to new business software comes down to four things: a fixed cut-over date, a list of what moves and what stays archived, a test import before the real one, and a short period where the old system is kept for reference and no longer edited.

Many switches that go wrong do so because two systems stay live at once. Invoices get created in both, customer changes land in one and not the other, and after a month nobody trusts either. The checklist below is built to avoid that.

Four weeks before: decide

• Pick the cut-over date. The start of a month or quarter is easiest, because open periods are short and reports line up. Avoid your busiest week.
• Name an owner. One person decides what moves, answers questions and signs off the test import.
• List what moves. Active customers and vendors with their contacts and addresses, and your products and services. Decide separately how open invoices and running projects will continue: some teams finish them in the old tool, others re-enter them by hand.
• List what stays behind. Closed years, finished projects and old correspondence usually stay in an archive you can still open.
• Check your exit from the old tool. Find out how it exports each record type, and in which format, before you depend on it. Our guide to data portability lists the questions to ask.

Two weeks before: prepare the data

• Export a CSV per record type from your current tool: one file for customers, one for contacts, one for items, and so on.
• Clean while it is small. Remove duplicates and test rows, split combined columns, and use one date format. How to clean your data before an import has the full list.
• Give every record a stable ID. Related rows find their parent through it, so a contact lands on the right customer.
• Run a test import with ten rows per file, open the results and compare them with the source. Fix the file, not the records, so the real import is clean too.

Cut-over week: switch

When	What to do
Last day on the old tool	Finish the period's invoices, record the payments you received, then export the final files.
Cut-over day	Bring records over in dependency order, parents before children: customers before their contacts and addresses, then items.
Same day	Spot-check a handful of records against the old system and confirm the open balances match.
Next morning	Tell the team where the data lives now, and stop editing the old tool.

Open invoices deserve their own plan, since they carry amounts that must match exactly. How to bring over open invoices covers that case in detail.

After the switch: settle in

• Keep the old tool for reference, not for work. Many teams keep access for a few months to look things up, then cancel.
• Collect the small fixes in one list for two weeks after the switch, and handle them together.
• Review the cost. Count what the switch took in hours as well as subscriptions; what switching software really costs helps you add it up.

What usually goes wrong

• No fixed date. "We will move over the next few weeks" means two live systems for those weeks. Pick a day and say it out loud.
• Importing everything. Years of closed records make the import slower and the new system noisier. Move what you work with; archive the rest.
• Skipping the test. A mapping mistake on ten rows is a five-minute fix. The same mistake on the full file is an afternoon of clean-up.
• Forgetting the people. A short walkthrough for the team on cut-over day saves a week of questions. Show each person the two or three screens they will use most.

How Swiftly Workspace helps with the move

Swiftly Workspace imports CSV or XLSX files. Customers, their addresses and contacts, vendor contacts and items can be imported this way. On a Mac, an admin opens Administration, then Data Import:

1. Start a session, choose the record types, and click Download CSV Template to get the expected columns.
2. Fill the template from your exported file, then Upload it. The rows are staged for review, not saved yet.
3. Click Validate to check the staged rows, fix what it reports, then click Commit.

An optional Validate Identifiers check looks at VAT numbers and email addresses; it is advisory and never blocks the import. How to import data on a Mac walks through every screen, and working with CSV templates explains the columns. If you are moving from spreadsheets rather than another tool, start with our plan for moving off spreadsheets.

Frequently asked questions

What is a cut-over date?

It is the day the new software becomes the place where work happens. Records created before it live in the old system or are imported; everything after it is created in the new one.

Should I run the old and new software in parallel?

For a day of checks, yes. For weeks of real work, no: two systems of record drift apart fast. Keep the old one for looking things up and do all new work in the new one.

Who on the team should own the switch?

Someone who knows the data and has time to answer questions, often the person who does the invoicing today. One owner makes decisions faster than a committee.

How long should I keep access to the old software?

Long enough to answer the questions that come up after the switch, often a few months. Before you cancel, export everything you may need to keep for your records, and store the files somewhere safe.