Services · Data migration
Master data, open balances and years of transaction history moved across with automated reconciliation at every step. History loads read-only, so your reporting continuity is never broken by the move.
The work
Migration is where ERP projects quietly lose their history. The new system goes live with opening balances and a year of transactions, the auditors ask a question about the year before, and the answer lives on a decommissioned server nobody can log into. It does not have to be that way. AlpineERP's import tooling takes structured data from any source, and the hard part is not moving rows, it is deciding what each column means.
We extract from whatever you have (a competing ERP, an ancient Sage or QuickBooks install, or fifteen years of spreadsheets), cleanse and de-duplicate it, map it to the target model, and reconcile after every load. Transactional history lands read-only, so period comparisons continue to work across the cutover date without polluting open items.
What you get
Named up front so the engagement has a definition of done.
Every source field matched to its target, with explicit decisions on the unmappable ones: recorded, not improvised. This document answers the auditor's question two years from now.
Duplicate customers collapsed, stale items retired, supplier records normalised. Migration is the one moment fixing this is cheap; afterwards it is archaeology.
Control accounts, subledgers and stock valuation tied to the closing trial balance of the old system, with a variance report signed off by your finance lead before go-live.
Prior years loaded so comparative reporting, customer history and item trends survive. Queries work across the cutover; nothing can be edited in the past.
Pricing
No day rates and no sticker price. The estimate is derived from your situation. Each answer moves it, and anything genuinely unusual is scoped rather than guessed.
Estimated data migration cost
$0
fixed, one-time
An estimate, not a quote. We confirm the fixed price against a written data map before extraction starts.
Platform plans are priced separately on the pricing page. This estimate covers the data migration itself.
Questions
Anything that can produce structured exports: competing ERPs, Sage, QuickBooks, Xero, Tally, Access databases and spreadsheet estates. AlpineERP's data import handles the destination side; the work is in extraction, cleansing and mapping.
Two full prior years as the working default: enough for period comparisons and trend reporting. Deeper history is available and sometimes required by regulation; the only wrong answer is zero, which breaks reporting continuity.
No. Extraction is read-only against the source. The old system stays untouched until the parallel run closes, and typically stays available read-only afterwards for exactly the audit questions described above.
Matching keys agreed in the field map, fuzzy matching on names for customers and suppliers, and trial loads that are reconciled (not eyeballed) before the next pass runs.
