Guide ยท Investor
Two stacks after an acquisition
We just acquired a 3PL on a different TMS. What do we do with two stacks?
Don't merge the TMSs on day one. Connect the two stacks through one integration layer so customers, carriers and finance see one company, decide the target architecture with the numbers, then migrate once.
ASSUMEDWe assumed two operating companies on different TMSs and different accounting systems, with some shared customers.
Your stack, as you described it
Where people are the glue
- Finance consolidates in spreadsheets
- Shared customers get two invoices and two trackers
Three ways through
- Use what you haveFor a quarter
Run both. Pick one accounting system first; the TMS decision gets better once you can see margin by customer across both books.
- ConnectWhat we'd do
One integration layer carrying both TMSs into the chosen accounting system, shared customer connections and one reporting view, with every connection documented for the migration that follows.
- BuildNot now
Acquisitions are where custom builds go to die. Build after the migration, if at all.
What happens next
- Our M&A team looks at integration debt before it becomes synergy leakage.
- A 100-day plan that sequences accounting, reporting, then TMS.
- Run keeps both stacks connected while you decide.
Have a different stack? Ask the guide.
Ask a follow-up