Migrating Twinfield to Yuki, what do I watch out for?
Twinfield is ledger-oriented, Yuki is document-oriented. The biggest pitfall is open AR/AP and how Yuki handles dimensions (lighter than Twinfield).
Try this first
- 1Close Twinfield on a quarter boundary, do not switch mid VAT period, that complicates the return.
- 2Export all open AR/AP and balances, import into Yuki via the starting-admin wizard.
- 3Keep Twinfield read-only for at least a year, do not delete for the retention obligation and accountant checks.
- 4Train your team on Yuki's document flow, fundamentally different from Twinfield's ledger focus.
- 5Check if your Twinfield links (CRM, time tracking, payroll) work with Yuki too, not always the case.
When to bring us in
If you have many cost centres or project administration in Twinfield, we can pre-test the Yuki translation.
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.