Will original document numbers, created dates and user references be preserved when we migrate to Sage X3?
Yes. We carry them across. Where Sage X3 cannot store one of them natively, it is kept in a custom field or reference on the migrated record, so every record can be traced back to the system it came from.
If Sage X3 can't natively support an old record type, what are my options?
We handle it case by case. While mapping your data, we identify every record type without a direct counterpart in Sage X3, review sample records from it and propose how it can be represented, based on what Sage X3 supports: map it to the closest native object, create a custom field or object, fold it into the parent record as text or a note, attach it as a file, or keep it in a read-only archive. You choose the approach, we write the migration scripts to place the data there, so it comes across in the form you choose instead of being left behind, and you see how it looks in a sample migration before we run the full set.
Will migrating to Sage X3 send emails or notifications to customers, our team or anyone else?
No. Before the sample or full migration starts, we confirm with you that nothing in Sage X3 will send messages about the migrated data: we import with notifications switched off wherever Sage X3 allows it, and pause any automation that could send them or give it a condition that skips migrated records. We only proceed once you have confirmed it. If you want anyone told about the move, that message is sent separately, once the migrated data has been checked.
Can you migrate data that Sage X3 can't take in through an API?
In many cases, yes. Where something can't be written through an API, we recreate it through the application itself where the interface allows it, and where that work is repetitive we script and automate it. We tell you up front which items are handled this way, because recreating them through the interface can add time to the schedule.
What happens if Sage X3 requires fields our current data doesn't have?
We check Sage X3 for required fields your current data cannot fill and bring each one to you before those records are migrated. Together we agree how each one is handled, such as a mapping from an existing field, a default value, or, where Sage X3 lets that field be made optional, setting it to not required for the migration so you can make it required again once the migration is complete. The migration then runs with that rule applied, so no records are rejected or left behind.
We use a lot of custom fields. Can you map them to Sage X3?
Where Sage X3 has a place for them, yes. Each migration is a custom script written for your project, so your custom fields and structure are mapped to Sage X3's model rather than forced through an import template. Where field types differ, such as a value stored as text in your current system that Sage X3 needs as a number, the script converts it. We agree the mapping with you and prove it on a sample migration before the full run.
Will links between our records still work after we migrate to Sage X3?
Yes. We move your data in two passes. The first pass creates every record in Sage X3 and stores its new ID. The second pass goes back and points each reference at the new record, so links between records lead to the right place.
What data will be migrated to Sage X3, and how will each type of record map?
It depends on your current platform and the scope you choose, but it is usually the core records and everything attached to them. Before anything runs, we send you a migration checklist showing where each type of record lands in Sage X3, including anything that won't move, and you confirm the scope.
What happens if some of our field values are longer than Sage X3 allows?
We handle it in the migration scripts. Fields where Sage X3's limit is shorter than your data are identified while we map your data, the handling for each one is agreed with you before the migration runs, and you can check the result in the sample migration before the full run.
Will the migration delete or overwrite any data that's already in Sage X3?
No. The migration adds your records alongside what is already in Sage X3, and nothing there is deleted without your confirmation. Where an incoming record matches an existing one, we link to the existing record rather than creating a second copy, and corrections to migrated records are made as updates wherever possible rather than by deleting and recreating them.
What happens if Sage X3 rejects some of our records during the migration?
We log each rejected record, fix the cause and push it again. Common causes, such as a required field your data doesn't fill or a value in a format Sage X3 doesn't accept, are agreed with you and handled in the migration scripts, and the scripts can be re-run safely without creating duplicates. When the migration finishes, you get a list of every migrated record and of anything left out, with the reason.
How do you check our chart of accounts mapping before we migrate to Sage X3?
We review it ourselves rather than taking it as given. Each account in your current system is mapped to its account in Sage X3 in the migration checklist, we check that mapping before anything moves and raise any account that looks wrong with you to confirm, and the sample migration then shows transactions landing on the mapped accounts. After the migration, balances are reconciled against your trial balance to confirm each account ties out.
Will our chart of accounts be copied exactly into Sage X3, or can you map it to a new or simplified chart of accounts?
Either. If you keep your current chart of accounts, it is recreated in Sage X3 as closely as its structure allows. If you're moving to a new or simplified chart, we map every old account to its new account with you in the migration checklist before anything moves, so balances and transactions land on the right accounts.
We have several companies or subsidiaries in our current system. Can you migrate them all to Sage X3, and how will they be set up there?
Yes. Each entity is migrated with its own records, and the set-up in Sage X3 follows how it handles multiple entities: where it keeps each entity as a separate company, each of yours is migrated into its own company. We agree the structure and the scope for each entity with you before the migration, and reconcile each one separately.
Do you migrate our full transaction history to Sage X3, or only opening balances?
Full transaction history is our standard approach, not just opening balances. That covers the chart of accounts, opening balances reconciled against your trial balance, general ledger transactions and journals, customers and suppliers, invoices, credit notes, bills and payments, and bank accounts. If you'd rather start with opening balances only, a shorter history or summarized monthly figures, we can scope it that way instead.
Can you migrate our books to Sage X3 if some accounts aren't balanced correctly, or do we need to fix them first?
Yes, you don't need to fix them first. We migrate your books as they are, so an account that doesn't balance today comes across the same way and doesn't block the migration. If you want the books cleaned up first, that is accounting work for your accountant or an accounting firm, and we can work alongside them.
Will our historical transactions be posted in Sage X3 in the periods they actually happened, rather than all in the current period?
Yes. When full history is migrated, each transaction keeps its original date, so it lands in the period it belongs to. Where reconciling entries are needed, we prepare them per year and per entity as well, so each historical period ties out on its own instead of everything flowing into the current year.
How do you handle customizations and third-party add-ons in our current ERP when we move to Sage X3, especially ones with no documentation?
We work from the data your customizations hold, so missing documentation doesn't stop them being migrated, as long as that data can be read from your current ERP. An engineer reviews the records each customization and add-on holds, connecting to the database directly for on-premises systems, writes the migration scripts to include them, and records each one in the migration checklist, which documents how it maps to Sage X3. Where Sage X3 structures data differently, such as shorter field lengths, the scripts handle the conversion, and you validate the result on a sample migration before the full run.
Superhuman Docs (Coda)
Claude, 
ChatGPT or 
Cursor. Describe the move in plain English; the agent runs it.
Notion
Slab
ConfluenceSoon
Google DocsSoon
