Will original ownership, authorship and created dates be preserved?
Yes. Created-time metadata is carried across, and ownership and authorship are carried across where the original users are set up in Sage Intacct. Where Sage Intacct cannot store one of them natively, it is kept as embedded metadata on the migrated record.
If the new system 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 Intacct, review sample records from it and propose how it can be represented, based on what Sage Intacct 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 the migration set off automations or 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 Intacct will send messages about the migrated data: we import with notifications switched off wherever Sage Intacct allows it, and either pause any automation that could send them for the migration window or give it a condition, such as a suppression tag, that skips migrated records, which lets your live automations keep running for new 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 Intacct can't take in through an API?
In many cases, yes. Where something can't be written through an API, we recreate it through Sage Intacct's user interface 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 Intacct requires fields our Coupa data doesn't have?
We check the destination for required fields your source 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 Intacct 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.
How do you check our chart of accounts mapping before migrating our Coupa data to Sage Intacct?
We review it ourselves rather than taking it as given. Each account in Coupa is mapped to its account in Sage Intacct 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 Coupa chart of accounts be copied exactly into Sage Intacct, 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 Intacct as closely as Sage Intacct's 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 Coupa. Can you migrate them all, and how will they be set up in Sage Intacct?
Yes. Each entity is migrated with its own records, and the set-up in Sage Intacct 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 Coupa transaction history to Sage Intacct, 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.
If some accounts in our books aren't balanced correctly, can you still migrate them from Coupa, 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 Coupa transactions be posted in Sage Intacct 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.
Superhuman Docs (Coda)
Claude, 
ChatGPT or 
Cursor. Describe the move in plain English; the agent runs it.
Notion
Slab
ConfluenceSoon
Google DocsSoon
