Switching Software While Keeping Daily Work Running

Choose how the work will move

• Move a defined part firstStart with a team, location or type of work that can use the replacement without leaving other staff guessing where its records belong.
• Switch at an agreed timeMove the connected work together when splitting it across two systems would make daily tasks harder to manage.

A limited start lets people try the replacement with a manageable amount of work. It is useful when you can clearly identify which jobs belong in the new system.

A single switch may make more sense when everyone needs the same current schedule or stock records. Choose a suitable time and allow for the final record transfer and checks.

Neither approach removes the need to prepare. If both systems will be used for a while, agree which one staff should trust for each kind of information and who will resolve differences.

Decide what happens to unfinished work

List the quotes, jobs, appointments and other tasks likely to be open when you switch. Decide which move into the replacement and which will be completed in the old program.

If an order stays in the old system, explain where staff will record later changes, payments or delivery details. Avoid moving part of the order without a clear way to find the rest.

Give staff a straightforward rule for new work. For example, all new bookings from an agreed date could go into the replacement, while a named list of existing bookings stays in the old program until completed.

That rule is only useful if the necessary programs remain available. Check access dates before choosing a plan that relies on the old system.

Let staff practise the tasks they will perform

Give each person access before launch and let them complete the tasks relevant to their role. Ask them to find a record, make a change and correct a mistake themselves.

Include common interruptions, such as a customer changing an order or a job needing another visit. Check that the next person can see the updated information.

Use practice records and keep real customer messages or payment actions disabled in the practice setup. Make it clear which environment staff are using.

The guide to software demos, feedback and testing explains how to report a problem with enough detail for someone to reproduce it.

Prepare the final transfer and first working day

Choose who will coordinate the switch and who can decide whether to proceed. They need to know which checks must be complete, which problems would delay the change and who is available to help.

Account for records changed since the trial import. If staff need to stop entering information briefly, tell them when that will happen and how to record requests that arrive during the pause.

Check open work, important totals and staff access before starting normal use. Confirm where incoming enquiries and online requests will arrive.

Review scheduled reminders, invoices and other automatic actions in both systems. Enable them in the intended place so the same customer does not receive duplicate messages or requests.

Agree what to do if the switch needs to pause

• Pause before staff beginKeep using the agreed current process while a problem with the transfer or final checks is resolved.
• Respond after work has startedPreserve new records and changes, then decide how staff can continue without losing or repeating the work.

Write down what staff should do if an important task cannot be completed. They may be able to use an agreed temporary record, pause one part of the work or return to the old system if it remains available.

Returning to an earlier backup does not automatically preserve what happened afterward. Plan how new bookings, changed orders and completed payments will be accounted for before anyone restores older information.

Name the person who makes that decision and tells the team what to use. A short, clear instruction is more useful during a problem than several conflicting suggestions.

Follow the work through its first full cycle

Keep help available while staff settle in. Review questions and problems regularly, giving priority to anything that prevents work from being completed or affects customers.

Follow the first jobs through to completion, including any later invoicing, stock adjustments or reporting. A successful first morning may not reveal an issue in a monthly task.

Keep the old records accessible for as long as agreed, then retire the old system once the relevant work and checks are complete. Confirm that staff can still find the history they need before cancelling access.

Your next step

Write a changeover note that answers four questions: where does new work go, what happens to unfinished work, who helps staff and what happens if the switch needs to pause? Review it with the people doing the work before choosing the final date.