Define what the migration needs to preserve
An accounting migration should begin with the records and functions the business needs after the change. Yudey helps organise a defined transfer project, from the source information through to an agreed opening position. We ask why the system is changing, which periods matter and which users depend on the records. A new subscription alone does not determine what must be transferred.
The proposal identifies the source and destination, entities, dates and data categories. Full transaction history, opening balances and access to an archived system are different approaches with different implications. We discuss those choices before implementation. The project should not assume that every attachment, audit trail or custom field can move automatically between products with different structures.
Establish a reliable cut-off and source position
The agreed preparation can identify a migration date and a reconciled record set. We ask which reporting periods remain open and how transactions entered during the transition will be handled. Without a clear cut-off, the same activity can be omitted or duplicated across systems. The plan therefore records where new transactions should be entered at each stage.
Opening balances and outstanding customer or supplier items need supporting evidence. We identify unresolved differences before treating them as a migration problem. A transfer can reproduce inaccurate source records faithfully, so successful import is not proof of accounting accuracy. Historical clean-up is separately scoped where the starting position requires more work than the agreed transfer project.
Map records and settings deliberately
The migration plan can compare account categories, customer and supplier records, tax settings and relevant tracking fields. We identify items that do not have a straightforward equivalent and agree how they will be handled. The business or responsible accountant confirms accounting decisions. We do not silently assign a new treatment just because the destination system uses a different default.
Attachments, references and links to other tools also need attention. The scope states which are included and what remains available through an archive or other record source. Government guidance explains the need to retain company accounting information. [1] The retention plan should reflect those obligations and the business's actual needs, rather than assume that closing the old account is harmless once headline balances match.
Compare the result against agreed criteria
The project can compare balances, outstanding items and representative records between the systems. We agree what counts as a satisfactory match and how differences will be investigated. The comparison should use identifiable dates and versions, so later changes are not mistaken for failed transfer. Exceptions remain visible until resolved or expressly accepted through an appropriate process.
The checks are scoped to the migration and do not provide a statutory audit opinion. A sample transaction check cannot establish that every historical tax treatment was correct. We distinguish transfer validation from broader accounting review, with additional professional work identified where needed. The business receives a clear account of what was compared and what remains outside the checks.
Protect continuity during the change
Bank feeds, invoicing and integrations may need a controlled transition to avoid duplicate imports or interrupted work. We identify the actions and who authorises them. Disabling an old connection or closing a subscription requires a deliberate decision after the agreed records are preserved. We do not delete source information merely because the new environment appears operational.
User roles and administrative ownership also need a handover. The plan can identify who retains access, how the accountant receives the required records and what evidence is stored outside the old platform. Ongoing support, staff training and future tax submissions are separate unless included. A migration project should leave responsibilities clear after the transfer team stops working.
Agree the handover and project fee
Your agreed output can include the mapping decisions, comparison results, unresolved exceptions and record-retention instructions. Approval of the opening position is recorded before the new routine is treated as established. If additional history or integrations are requested during the project, their effect on scope and timing is assessed rather than assumed within the original transfer fee.
Fees depend on data volume, source quality, systems and validation depth. The GBP quotation identifies applicable VAT and separate subscription, clean-up or training costs. Begin with both systems, desired transfer date, last reconciled period and essential history. We will clarify access and evidence needs before receiving exports or making changes to live records.
Official information behind this service
Sources checked on 7 September 2026. Use the linked guidance for subsequent changes.