ERP Selection, Migration & Ops-Finance Integration
Every hold period includes a systems project. Where portcos usually pick the wrong ERP, how the migration actually gets done, and how ops software wires into the ledger.
Every Hold Period Includes a Systems Project. The Question Is Whether It Gets Done Well or Badly.
The founder built the business on the accounting system that worked when it was smaller. QuickBooks Online, sometimes QuickBooks Enterprise, occasionally a legacy on-premise system nobody wants to touch. Operations run on separate platforms — Salesforce for the CRM, ServiceTitan or Procore for the field, Fishbowl or NetSuite for inventory, a mid-tier payroll platform, an expense tool. None of them talk to each other cleanly, and the reporting layer is a spreadsheet the controller updates manually.
The sponsor's report says the same thing every quarter: we need to see this data faster and we need to see it broken out differently. What the report doesn't usually say is that the data can't be produced faster or broken out differently in the current system stack — and closing that gap is a project, not a report format change.
We've selected, implemented, and cleaned up ERP systems for dozens of portfolio companies. What that experience buys is a realistic view of what each system actually does well, what it doesn't, what the migration timeline looks like, and how to keep the finance function running through the transition.
The Selection Question
What Actually Matters When Choosing an ERP.
The right ERP is rarely the most-marketed one. It's the one that fits the operating model with the least customization.
Industry Fit
Distribution has different needs than services. Project-based businesses have different needs than product businesses. Multi-entity operators need consolidation the single-entity operator doesn't. The ERP that fits the operating model with the least custom work is almost always the right choice.
Integration Ecosystem
The ERP has to connect to the ops systems already in use. Native integrations, mature middleware, or bespoke API work — each has cost and risk implications. Reviewing the integration path for each ops platform before the ERP decision usually surfaces the deal-breaker early.
Reporting Architecture
The dimensions the sponsor wants (customer, product, segment, location, project) have to be first-class fields in the ERP, not custom fields hidden behind reports. Systems that treat segmentation as an afterthought make sponsor reporting a permanent workaround.
Total Cost Over the Hold
License cost is one line item. Implementation cost, integration cost, ongoing admin cost, and the cost of the internal team required to run the system are the others. A cheaper license with expensive implementation and heavy admin is not cheaper.
Multi-Entity and Multi-Currency
If the portco is a platform for add-ons or has international operations, multi-entity and multi-currency support matter from day one. Retrofitting either later is painful; buying the right foundation is cheap by comparison.
Team Capacity
A system that requires a full-time admin the portco can't hire is the wrong system, regardless of the sales pitch. Match the system's operating requirement to the team's actual capacity.
The Migration.
Design phase (weeks 1–6). Chart of accounts design. Segment and dimension architecture. Approval workflow design. Integration architecture. Data cleanup requirements. If this phase is done well, the rest of the migration is straightforward; if it's rushed, everything downstream has to be rebuilt.
Build phase (weeks 6–16). ERP configured. Integrations built and tested. Historical data migrated. Cutover dry-runs. Parallel processing period where both systems run — the old system for operations, the new system for finance validation.
Cutover (a defined weekend or month-end). Final data conversion. Cutover to live. First close on the new system with extra hands on deck. Every discrepancy caught in the first month gets resolved before it becomes noise.
Stabilization (weeks 18–30). The first three closes on the new system are always harder than the fourth. We stay through stabilization to make sure the finance function is running cleanly before we step back.
Wiring Ops Systems to the Ledger.
Salesforce or the CRM. Bookings, backlog, and revenue recognition triggers should feed automatically. Manual data entry from opportunity closed-won to revenue booked introduces errors and lag.
Field service or project systems (ServiceTitan, Procore, Jonas, others). Job costing, WIP, and revenue-recognition triggers flow from the operational system to the ledger. Getting this right is often the difference between an accurate monthly close and a chronically messy one.
Inventory and warehouse systems. Landed cost, standard cost updates, and cycle-count adjustments should post to the ledger through automation, not through the controller's spreadsheet.
Payroll, expense, and treasury. Bill.com or similar for A/P workflow. Expense platform for corporate cards and reimbursements. Treasury for bank reconciliation and cash management. Each integration replaces manual data entry with reliable automation.
If the Systems Project Is on the Roadmap
Design Well Before You Buy.
We do ERP selection, migration, and ops-finance integration for portfolio companies — independent of any vendor. The vendor sells software; we build the finance function that runs on it.
Tell Us the Situation
The Portco, the Current Stack, and Where It's Breaking.
What's in place today, what the sponsor's requirements are, and what the timeline looks like. Same-day response.
Schedule a Discovery Call
We’ll reach out within one business day.