Every acquisition lands on Guardian Restoration’s finance team the same way: another set of books to close, another chart of accounts to learn, another reconciliation before the parent company can see one consolidated number. Guardian’s private equity owner buys companies quickly, and each one arrives on whatever system it already ran. One came on Sage 300, another on QuickBooks, another on ComputerEase.
Sage Intacct’s multi-entity model is built for that problem, and Guardian is using it in an active phased rollout: one place for consolidated financial reporting, with each acquired entity brought in after workflow review, data preparation, and training. The pace is deliberate. Forcing every company through a single cutover concentrates risk the software cannot absorb, and the rollout still needs owners for data cleanup, process standards, approvals, and exceptions.
This is an implementation-side view of an active rollout, written before outcome numbers exist. We implement and support these systems for a living. For this case, we sat down with Tina Rehberg, our Senior Sage Intacct Consultant, Audra Speth, our Customer Success Manager, and Troy Guevara, our Construction Technologist focused on construction ERP.
For scale, Discovery Land is a separate Alta Vista Technology multi-entity account where the same deliberate rollout discipline has carried past 300 entities. Guardian Restoration shows the PE-backed acquisition pattern; Discovery Land shows what the operating pattern looks like at hundreds of entities.
Guardian Restoration’s starting point
Guardian Restoration is a private-equity-backed restoration group whose PE owner purchased multiple different types of companies and is bringing them under a shared parent reporting structure.
The acquired companies did not arrive from one system. Tina named Sage 300, QuickBooks, ComputerEase, and other systems as part of the legacy environment. The rollout is active and ongoing, with entities brought in individually as each one is ready.
Moving one entity at a time keeps finance from treating local workflows as noise. Leaving every company alone indefinitely creates another separate set of books, reports, and reconciliations with each acquisition.
Tina’s implementation habit is to hear the entity’s language before mapping it into Sage Intacct. One company may use “task” to mean an activity. Another may use the same word to mean a cost code. A Sage 300 company may already think in prefixes, base accounts, and sub-accounts. A QuickBooks company may be moving from general-ledger-level accounting into project, cost-code, and cost-type detail for the first time.
Why the parent view matters
Acquisition-heavy groups create controller pain quickly when every acquired company remains a separate finance world. Ownership wants a consolidated picture. The controller has to answer from different books, different account structures, different reporting routines, and different levels of data quality. Every acquisition the group makes is also a reporting problem it inherits.
Audra sees acquisitions as one of the clearest reasons finance teams care about a multi-entity setup. She described the controller’s reaction when another acquisition lands: “In the old world the controller is thinking, ‘Great, now I have to prepare another set of books and manage another chart of accounts.’”
Consolidation does not remove the accounting work. The books still need to be built. Data still needs to be reviewed. The acquired team still needs to learn how billing, AP, coding, and reporting will work after go-live. The difference is that the work ends with the entity inside the parent reporting setup, done once, as part of a repeatable onboarding.
Tina described the PE value the same way: “Being able to bring entities in on whatever timeline is convenient, and consolidate each up to the top level, is what makes it easy for a PE group to absorb everything they’re buying.”
Audra uses the same governance language for large multi-entity rollouts: “The whole thing is a structured, deliberate attempt with constant check-ins, never a blitz.”
Why Guardian Restoration is moving one entity at a time
Guardian Restoration’s rollout is phased. The sequence gives finance a repeatable way to bring acquired companies in when the data, workflows, and people are ready.
The account mapping work changes by starting system. Tina told us a Sage 300 client is often already closer to the structure needed in Sage Intacct because prefixes, base accounts, and sub-accounts can be connected to dimensions, the fields used to tag activity by entity, location, project, cost code, cost type, and similar reporting needs.
A QuickBooks entity can be a larger conceptual move. Some teams are used to seeing accounting mostly at the general ledger level. After the move, they may need to code work with more project and cost detail than they used before. A team in that position needs more coaching and clearer examples during implementation, and a fair amount of patience from parent finance while the new coding habits take hold.
Deciding what to standardize and what to keep local
The parent company needs control over the reporting setup. If every acquired business keeps every local preference, the consolidated report may sit on top of a patchwork that finance still has to explain manually.
The acquired company also needs a fair review. Local teams often know why invoices are sorted a certain way, why a payment routine exists, and which fields people use to answer customer questions. Some habits should change. Some point to real operating needs.
Tina calls the useful exceptions “little wins inside the core.” By that she means small supported adjustments that help the local team work cleanly without redesigning the parent setup. For example, the core template may not change for one company because other entities depend on it, but a supported custom field may help that entity sort AR invoices or payments in a way its team can use.
What changes after an entity is live
After an entity is brought in, the local team works in the parent company’s setup, and parent finance has a cleaner path to include that entity in top-level reporting.
Go-live moves the acquired company into the parent operating structure for reporting. Some friction points and legacy references linger past the cutover date, and the remaining cleanup is handled inside a repeatable onboarding process.
For the controller, another acquisition no longer has to become another permanent island. The work still exists, but it is attached to an onboarding motion the team can repeat.
What to decide before you scope a similar rollout
An entity-by-entity rollout works best when leadership makes the operating decisions before asking the software to enforce them. Finance and operations should agree on what must standardize, where exceptions can be reviewed, and who gets final approval when a local workflow conflicts with parent reporting needs.
Before scoping a similar rollout, make these decisions explicit:
- Which entities are ready to move first. Readiness includes data condition, local team capacity, workflow clarity, and whether the entity can work inside the parent reporting setup.
- Which legacy systems are in play. Sage 300, QuickBooks, ComputerEase, and other systems create different mapping, cleanup, and training conversations.
- What data must come over first. Opening balances need an owner, a review process, and a clear decision about what history stays in the legacy system.
- Which workflows are non-negotiable. Parent finance should define required controls and reporting rules before local exceptions start appearing.
- Which third-party systems matter. Identify project management, payroll, AP, and other operational systems early, because the ugly failure is finding out during testing that the acquired entity’s coding structure does not match what the integration expects.
- Who approves exceptions. A local request may be valid, but someone needs authority to decide whether it fits the parent reporting setup.
We asked Troy what he wants buyers to ask before signing a scope. His questions were direct: “What does data migration look like? Can we connect third-party platforms? What do we need to change to make this system work for us?”
The last question decides whether consolidation becomes real. A rollout can have the right account structure and still struggle if leadership will not define the process decisions behind it.
Troy puts the leadership issue plainly: “Software can’t fix a management problem. If leadership tolerates a bad process, the software isn’t going to enforce what leadership won’t.”
The useful lesson from Guardian Restoration
What carries to any acquisitive group is the operating model: build the parent reporting structure first, then onboard acquired entities one at a time. A single mass conversion is the move to avoid.
A PE-backed construction or restoration group needs a repeatable way to absorb acquired companies without pretending they are all the same. In this rollout, Sage Intacct is where entities are being brought for top-level reporting, but the software is only one part of the work.
The harder decisions are human and accounting decisions: which entity moves first, how legacy accounts map, who signs off opening balances, what reports parent finance needs to trust, which workflows must change, and which local needs deserve a controlled accommodation.
If those decisions are clear, an entity-by-entity rollout gives the group a practical way to keep acquiring without rebuilding finance from scratch every time. If those decisions are avoided, the system will inherit the same confusion the business already had.
The right foundation for your next stage of growth
Our team of experts is here to help guide you every step of the way. Let’s start your ERP journey today!
