Contact
Tell us what you're leaving, where you're going, and how much history matters.
You do not need to prepare a perfect specification. A rough picture of the source system, destination, entities, years and timing is enough to start.
Useful starting information
What helps us scope a migration
- Current accounting / ERP system
- Destination platform
- Number of legal entities / companies
- Years of historical data required
- Approximate transaction volume
- Foreign currencies
- Departments, projects, cost centres or other dimensions
- VAT / tax registrations
- Target go-live date
- Implementation partner, if appointed
Prefer email?
Complex project?
We may recommend a migration-readiness review first.
Where volumes, source-data quality, restructuring or destination requirements are not yet clear, we may scope the data separately before confirming the full migration. This avoids pricing or promising a delivery plan before the real complexity is understood.
Before we begin
What we need to scope a historical migration.
Source, destination, entities, history, volumes, currencies, reporting dimensions and future-state design all influence the migration approach.
View migration requirements →