We are considering migrating from AFAS to Exact (or vice versa), what are the pain points?
AFAS and Exact target the same market but handle dimensions and HR linkage differently. The migration itself is a mapping job, the real work is process adaptation.
Try this first
- 1Inventory which modules you actively use (finance, HR, projects, CRM), not every AFAS module has a 1:1 Exact counterpart.
- 2Map ledger accounts and cost centres, AFAS dimensions do not always align with Exact divisions.
- 3Plan a cutover at the start of a financial year, opening balance to new environment and history as read-only in the old one.
- 4Train accountant and internal users in time, in our experience process resistance is bigger than technical resistance.
- 5Keep at least 7 years of readable access to the old admin for the Dutch retention obligation.
When to bring us in
With more than one entity or HR plus finance combined, such a migration gets complex, we can help plan the path.
See also
- Switching from Exact Online to Yuki, open items and history do not matchPackage migrations stumble on ledger mapping and open AR/AP. Without a mapping table you lose context.
- Twinfield to Exact, dimensions and cost centres go missingTwinfield uses dimensions, Exact uses cost centres and projects. The mapping is not one-to-one.
- Accountant asks for RGS mapping, your ledger does not follow RGSRGS is the Dutch standard chart that SBR filings and accountant software expect. Without mapping, every year-end is manual.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.