By Hugh O. Stewart

One of the biggest benefits of a Sage Intacct implementation is the opportunity to consolidate multiple entity accounting systems into a single source of truth.  

Whether you’re bringing together 10 or more QuickBooks company files, merging data from multiple ERPs after a series of acquisitions, or standardizing accounting across independent business units, the migration is your opportunity to redesign how your financial data is organized and consolidated — not just transferred from one system to another. 

Consolidating years of data from independent systems comes with some challenges: You’ll run into duplicate vendors and customers, conflicting charts of accounts, inconsistent naming conventions, diverse uses of additional dimensions, and inactive records that still appear in historical transactions. All of those issues have to be identified and resolved before the data can function as one cohesive system. 

Every successful multi-entity migration follows the same philosophy. Before you can configure and populate your accounting system, you have to build a single source of truth outside of the new system. 

Here’s the process we use at Platform Transition to consolidate multiple accounting systems — or dozens of company files from the same accounting platform — into a single Sage Intacct environment. 

Determine What Data Actually Belongs in the Migration 

The first step in a successful multi-entity migration is to determine what data actually belongs in the migration. 

At Platform Transition, we start every data migration by extracting the historical transactions you want to preserve. Those transactions tell us which master data elements actually matter during the migration period. If a vendor, customer, item, or account doesn’t appear in the historical transactions you’re migrating, it usually doesn’t need to be created, mapped or consolidated in the new system. Conversely, some of your most important master data may exist in inactive lists because it was used years ago but still appears in historical transactions that need to be preserved. 

This differs from a traditional ETL approach, which often begins by extracting every master data list from every source system and mapping everything within. That can lead to unnecessary time and effort spent mapping and de-duplicating records that have no impact on the migration. 

By using the historical transactions as our guide, we focus only on the master data that actually supports your financial history. This step also helps prevent one of the most common sources of migration errors: historical transactions that reference inactive or modified vendors, customers, or other master records that were overlooked because they no longer appear on active lists. Rather than discovering those problems during the import process and correcting them one at a time, we identify them at the beginning of the project and incorporate them into the migration strategy. 

Create a Single Source of Truth Before You Configure Sage Intacct 

When you’re consolidating multiple accounting systems, you have to create an independent source of truth outside of both the legacy and target systems. 

Each legacy system contains only part of the organization’s financial history, often with different charts of accounts, naming conventions, and master data structures. Before you can make any decisions about the target system architecture, you need to get a comprehensive picture of what kind of data structures you actually used across all your legacy systems.  

That’s where the scrub list comes in.  

The scrub list combines every historical transaction and every master data element that falls within the migration scope into a single spreadsheet. 

Once the scrub list has been established, we normalize the data so it aligns with the target system’s import structure. That means translating data from each legacy platform into a consistent format while preserving the accounting relationships and historical context that make the data meaningful. 

Build a Unified Master Data Strategy 

Once you’ve established a single source of truth, the next step is deciding what your master data should look like in Sage Intacct. 

This is called data mapping, and it’s where the migration shifts from a technical exercise to a strategic one. 

When you consolidate multiple accounting systems, your scrub list will almost certainly contain duplicate vendors, customers, projects, items, and other master data. Some duplicates will be obvious, while others will only differ by a slight variation in spelling or punctuation. For example, you might find records for “ATT,” “AT&T,” and “AT and T” that all refer to the same vendor. Other kinds of duplicates are not as straightforward to determine. 

Additionally, not everything that looks like a duplicate should be merged. 

Suppose each of your legal entities has a separate billing agreement with AT&T. In that case, keeping separate vendor records may be the better long-term design because it preserves entity-specific workflows and reporting. In other situations, consolidating those records into a single shared vendor may simplify maintenance and improve reporting across the organization. 

The data mapping step of a multi-entity migration gives you an opportunity to redesign your accounting architecture. For example, you might choose to consolidate separate location-specific accounts into a single account and use Sage Intacct’s Location dimension instead. Similar decisions can be made throughout your chart of accounts and master data structure to create a cleaner, more scalable reporting environment. 

To make sure the historical relationships within your legacy data are preserved, we also create an entity index within the data map. Each historical transaction gets assigned to the entity it originated from, giving you the ability to trace every transaction back to its original source when needed. 

De-Duplicate at Scale While Preserving Every Historical Relationship 

Once you’ve established your master data strategy, the remaining challenge is executing it consistently across millions of historical records. 

At that scale, you can’t rely on manually reviewing spreadsheets or using Find and Replace functions to identify potential duplicates. Nor is finding duplicate records the hardest part of the problem. 

The real challenge is preserving every historical relationship after those records have been merged. 

For example, if you decide that “ATT,” “AT&T,” and “AT and T” should all become a single vendor in Sage Intacct, every historical transaction that references those vendor records must also be updated to point to the new consolidated record. If the master data and historical transactions fall out of sync, you’ll encounter import errors and broken relationships during the migration. 

That’s why we built The Duplicate Suppression System™ (DSS). 

The DSS uses a proprietary matching algorithm based on Jaccard set theory to identify potential duplicate vendors, customers, projects, and other master data by comparing name variations, addresses, Tax IDs, and other identifying attributes. Rather than simply flagging possible duplicates, DSS also updates the data mapping and the Sage Intacct import templates at the same time. 

As master records are merged, the associated mappings and historical transaction references are updated automatically. That ensures every historical transaction continues to point to the correct master record throughout the migration process, dramatically reducing manual effort while preventing the mapping inconsistencies that commonly lead to import failures. 

By automating the repetitive work while preserving the integrity of the accounting relationships, the DSS allows our team to focus on the strategic decisions that require accounting expertise. 

Multi-Entity Migration is an Opportunity to Unify and Enrich Your Accounting Data 

Multi-entity migration is more than a consolidation exercise. It’s an opportunity to redesign your accounting data around the way your business will operate in Sage Intacct after your Go-Live rather than the way it evolved over years of acquisitions, multiple legacy systems, and independent business units. 

A well-executed multi-entity migration gives you a unified financial history that supports consistent reporting, better decision-making, and more long-term value from Sage Intacct. 

One of our clients, Coppermine Capital, asked us to consolidate 10 years of detailed historical accounting data from 95 separate QuickBooks company files into a single Sage Intacct environment. Before we could move any data into Sage Intacct, we had to establish a single source of truth for every transaction, customer, vendor, account, and historical relationship that appeared in each entity during the migration period. That process then served as a strategic blueprint for the rest of the implementation.  We also had to support a master data sync with 10 instances of Bill.com as part of the effort. 

At Platform Transition, we’ve completed nearly 3,000 entity migrations into Sage Intacct, including some of the largest and most complex historical data consolidations in the Sage ecosystem. Whether you’re combining a handful of company files or dozens of independent accounting systems, our methodology is designed to preserve your history while helping you build a better accounting architecture for the future. Schedule a meeting or request a quote to discuss your multi-entity migration project.