Migrate to Sage Intacct Seamlessly

Yes. We run a sample migration on your own data first, so you can review how your records look in Sage Intacct before the full migration goes ahead. We run validation scripts to confirm the record counts match your source, and you check the sample against your source records; if a field is missing or mapped wrong, or anything else needs adjusting, we fix it in the migration scripts and re-run the sample as many times as you need. The full migration only runs after you've approved the sample. On projects delivered in phases, each phase gets its own sample migration for you to approve.

Yes. If your system has an API, we read from it directly. If it doesn't, we work from a database export or flat files that your system can produce. In both cases we confirm the field mapping on a sample migration before the full run.

ClonePartner does the engineering side of the migration: extracting your data from your current system, mapping it to the structure of Sage Intacct and loading it with its relationships intact. Beyond what we agree as part of the migration, your team or your implementation partner configures Sage Intacct and your business processes, and we migrate into the setup they build.

We start by agreeing on a migration checklist with you, covering how each field maps to Sage Intacct. We then run a sample migration of a few hundred records, along with a separate verification report that compares the source and destination records, for you to review. Once you approve the sample, we run the full migration and finish with a delta sync just before cutover, so anything created or changed in the meantime comes across too.

Set up Sage Intacct first. It works best to configure it the way you want to work from now on, then we write the migration scripts to translate your old data to match that setup. That is cleaner than migrating everything as it is and reshaping it inside Sage Intacct afterwards.

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.

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.

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 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.

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.

We check Sage Intacct 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 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.

Where Sage Intacct 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 Intacct'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 Intacct 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.

Yes. We move your data in two passes. The first pass creates every record in Sage Intacct 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.

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 Intacct, including anything that won't move, and you confirm the scope.

We handle it in the migration scripts. Fields where Sage Intacct'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.

No. The migration adds your records alongside what is already in Sage Intacct, 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.

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 Intacct 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.

It depends on your Sage Intacct plan. Migrated records arrive as regular records in Sage Intacct, so whether they count toward its record or storage limits is set by Sage Intacct's pricing, and its own team or your implementation partner can confirm how your plan treats them. If limits are a concern, you can reduce what moves, for example by migrating only the last one or two years of history.

We review it ourselves rather than taking it as given. Each account in your current system 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.

Either. If you keep your current chart of accounts, it is recreated in Sage Intacct 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.

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.

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.

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.

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.

Most migrations complete within 1–5 business days, depending on data volume and complexity; very large migrations, such as several hundred thousand records, take longer. We provide a detailed timeline after the initial assessment and can often complete small migrations in under 24 hours.

No. Our migration process is designed for zero downtime. Your current platform stays fully operational throughout: the bulk migration runs in the background and the cutover is fast, so there is no disruption to your live business operations.

Mostly yes, and your team can keep working as normal, but leave the fields being migrated as they are, in your current platform and Sage Intacct, until the migration, including the final delta, is complete. The field mappings are set before the run starts, so hold off on renaming or removing those fields, and changing a migrated field's options, archiving it, or marking it as required or conditional can stop records from migrating. Where needed, and as agreed with you, we set the matching fields in Sage Intacct to active, not required and not conditional for the duration of the migration, wherever Sage Intacct has those settings. Other fields can be added or removed in the meantime. Also pause any AI agents, automations or rules in Sage Intacct that could act on migrated records, so they don't fire on historical records as they arrive; if some must keep running for live work, we can instead agree a condition that makes them skip migrated records. Once the migration is complete, you can switch them back on, restore those field settings and rename fields freely.

Before anything moves, we pull your data into a staging environment and prepare a reconciliation pack of record counts and totals from your current system. You then review a sample migration to see your own records in Sage Intacct. After the full migration we reconcile again, checking the counts and totals in Sage Intacct against those starting figures.

No, reconnecting integrations is not part of the migration. Your team connects each tool to Sage Intacct after cutover, and if you want a custom integration rebuilt, we scope and quote it as separate work.

Yes. Any records that cannot be placed in Sage Intacct are listed for you, and we hand them over as a data export. That way you keep a complete copy of your data, even after you stop using your old platform.

Not without your go-ahead. Delta syncs check incoming records against what is already in Sage Intacct so they don't overwrite your team's changes, and records your team has worked on since the migration are left out of any reimport. If a re-run is needed, for example after a mapping change, it can update records that were already migrated, so we confirm with you first which records it will touch.

It can happen where the two systems record certain things differently. Inventory valuation methods can differ between accounting systems, and some transactions, such as ones split between entities, have no one-to-one equivalent and have to be posted another way. That's why reconciliation is part of the migration: we compare the expected balances against Sage Intacct's general ledger and trial balance, and agree reconciling entries with you for any difference that remains.