CAP-03Migration
Data processing and migration.
Moving accounting, payroll and HR data between systems, with balances reconciled on both sides.
§ 01Overview
Overview
A migration is a reconciliation exercise with a deadline. The data has to arrive complete, in the right codes, with the same balances it left with, and the old records have to stay available for as long as the law says.
The proposed method works in stages with a control total at each one, a trial load before the real one, and a parallel run before anyone switches off the old system.
Input
- Legacy system exports
- Masters: accounts, parties, employees, items
- Open items and balances
- Historical transactions (agreed periods)
Output
- Mapping workbook with sign-off
- Trial-load reconciliation
- Cut-over checklist
- Readable archive of the old data
§ 02What it covers
Scope, line by line.
Extraction
Data taken from legacy software and spreadsheets, with record counts and totals noted at source.
Cleansing
Duplicates, formats, dates and master data put right before mapping, with each fix logged.
Mapping
Old codes mapped to new charts of accounts, parties, tax codes and pay heads, signed off before loading.
Trial loads
A full rehearsal into a test environment, reconciled balance by balance.
Cut-over and parallel run
A dated cut-over plan and a period running both systems until the results agree.
Archive
The old data kept readable and read-only for the retention period the law requires.
Areas of operation
§ 03How it runs
The migration line,
stage by stage.
The same five-stage discipline as every request: intake, validation, processing, review and delivery, shaped for this work.
§ 04Controls
Checks built in,
not added on.
Intended practice · to be confirmed
- Record counts and control totals matched at every step
- Mapping signed off before any load
- Source data kept read-only
- A rollback point before cut-over
RolesWho does what
You keep
- Sign-off on mapping and cut-over
- The decision to switch off the old system
- Ownership of both systems
AKOS does
- Plan the migration and the checks
- Extract, cleanse and map
- Run trial loads and reconcile
- Support the parallel run and archive
Personal data handled in this work follows the data-handling model on the How it works page.
§ 05Questions
Common questions.
Q01How much history should we migrate?
Usually open items and balances plus the periods you actively use. Older periods can stay in a readable archive, provided the retention rules are met. The note on this website sets out the main ones.
Q02Do you keep a copy of our data?
Only for the duration and purpose agreed in writing, and it is deleted afterwards. See how data is handled on the How it works page.
MoreOther capabilities
Other proposed capabilities
Was this page useful?
Sends only this page's address and your answer. No personal data is collected.
NextEnquiry