Start with what you use today: paper, spreadsheets, WhatsApp or an existing system. We’ll work out what needs to move and help your team check it before switching.
See what a migration check catches.
Source-to-target reconciliation compares the old and new records. An import can contain every item and still have the wrong stock quantity.
Try this small example, correct the missing quantity and run the check again.
Use an agreed hypercare period for additional checks and staff support. Decommission the old system only after acceptance and retention review.
Handover & support contacts
Know where the team works during the switch.
We name the working system at each point, plan any pause and account for new orders and payments.
Before the move
Current system
Daily work continues
New system
A separate trial for checks and staff practice
The switch window
Current system
Updates pause where required
New system
Final changes, final checks and your go-ahead
After approval
Current system
Retained or archived as agreed
New system
Your team starts daily work with agreed support
If we need to go backPreserve and reconcile new transactions before returning to the previous system. An older copy alone will not contain work entered after the switch.
See what your team reviews.
These sample documents show the decisions and checks to record for your project. They use fictional data or blank fields.
We’ll work through the practical details with you before agreeing a cost or date.
Do we have to change everything at once?
We’ll first check whether one task or department can move on its own. For example, stock records might be a useful starting point while other work stays as it is. Some tasks depend on each other, so we’ll explain those connections before recommending a phased move or a larger change.
Will our business need to stop during the move?
There may be a planned pause while the final records are transferred and checked. We’ll work out the likely interruption, a suitable time and how to record any new work during it. This depends on what you use today and how much information needs to move; we’ll explain it before agreeing the date.
What will the move cost?
We’ll first look at the amount and condition of your records, what can be copied automatically and what needs manual work. The proposal will separate moving and checking records, staff training and ongoing costs. If an existing software provider charges to release your information, we’ll identify that before you commit.
What if the checks find a problem?
Missing records, unexplained balance differences or a failed critical task should block the switch until resolved. An agreed exception must identify the affected records, the business impact and the person accepting it. If a problem appears after launch, the fallback must preserve new orders and payments before anyone returns to the old system.
Can you move records from our existing ERP?
We’ll check its name and version, available CSV or Excel exports, APIs, authorised database access and any vendor export fees. We’ll also check whether attachments, audit history and links to other tools can be extracted. A spreadsheet export of invoices may omit payments or documents, so feasibility is confirmed from a trial, not the product name alone. For an initial enquiry, send the system name; please don’t send passwords or confidential records through the form.
Will old documents, history and passwords move too?
We’ll decide separately whether to move attachments, completed transactions and audit history, or keep them in a searchable archive. Existing staff passwords should not be collected; we’ll plan new invitations, password resets or a supported identity-provider connection. Software licences, custom reports and third-party connections also need their own handover plan.