elevate techConsulting Group

Technology integration after an acquisition

What should the first 100 days of IT integration look like?

The first 100 days of technology integration should stabilize both businesses, inventory every system and contract, decide which system will be the system of record for each kind of data, deliver a few quick wins, and end with a costed roadmap. They are not for finishing the merger of systems. They are for learning enough to merge them safely.

After a deal closes, there is pressure to show progress on integration. In technology, the right early progress looks quiet: nothing breaks, you find out what you own, and you make decisions in the right order. This plan is the backbone of our technology integration after an acquisition work, and it applies to bolt-on deals, mergers and carve-outs alike. If you are still before the deal, start with the technology due diligence checklist.

What is the goal of the first 100 days?

Three things. Keep the lights on in both companies. Know exactly what you now own. Decide where the combined company is headed, and in what order it will get there. Everything else can wait. A company that tries to consolidate email, ERP, CRM and payroll in the first month usually spends the second month repairing what the consolidation broke.

What happens in days 1 to 30?

The first month is about safety and visibility: how you stabilize both businesses.

Days 31 to 60: how do you take inventory?

Now build the complete picture. List every system, who owns it, what it costs, what it connects to and when its contract ends. Include the quiet ones: spreadsheets that run a process, a tool a department bought on a credit card, an integration a former employee built.

Inventories always turn up more than anyone expected. On a pro audio carve-out, 179 systems and 15 entities belonged to the parent company, with a fixed deadline to stand them up independently. Nobody in the business could have listed them from memory. For each system, record:

Want a quick read on how your own systems fit together before you add another company's?

Take the Systems Check

What is the two of everything problem?

This is what the inventory will show. You now have two ERPs, two CRMs, two payroll providers, two sets of customer records and often two versions of the truth. The expense of duplicate licenses is the smaller part. The larger cost is people re-keying data, reports that cannot be compared, and a leadership team that argues about whose number is right.

Our multi-brand auto parts distributor project showed this clearly. The company had two systems of record that disagreed, and a single order entered in the new ERP could break in the old one. Running two of anything means every hand-off between them becomes a risk. List every place where the two systems overlap and every place where data crosses from one to the other. Those crossings are where problems hide, and they will shape your roadmap.

Days 61 to 100: how do you decide the systems of record?

A system of record is the one place where a kind of information is true: customers, items, orders, general ledger, employees. For each, choose one. The decision is not always "pick the bigger company's system." Ask which system supports the business as it will be, not as it was.

Data or processOptionsQuestions to settle
General ledger and financeKeep A, keep B, replace bothWhich handles both entities, and what does the lender or sponsor need to see?
CustomersOne master CRM or ERP recordHow are duplicates resolved, and who owns the master?
Items and pricingOne item masterDo the two companies name and cost things the same way?
People and payrollOne platform or twoState rules, benefits, and timing of any move
Email and identityOne tenant and one sign-inSecurity, access and domain plan

You may decide to run two systems for a while on purpose. That is a legitimate choice if it is written down, has an end date and has an owner. The danger is running two by accident.

Which quick wins should you take?

Pick wins that are cheap, visible and low risk. Typical examples: cancel duplicate or unused subscriptions once you know what depends on them, build one combined weekly view of cash and revenue, close security gaps, and automate a single painful re-keying step between the two companies. Quick wins earn trust for the harder decisions. They are not a substitute for the roadmap.

What should the roadmap contain by day 100?

A short document the CEO and the board or sponsor can read in one sitting.

The consumer products carve-out is a good example of the shape. After a three-week assessment, the team delivered a twelve-month transition plan and budget, and the deal closed. The plan did not do the work. It made the work possible to commit to. You can find more on the sequence in why systems that should agree do not, which covers a similar pattern in multi-location companies.

What can wait until after day 100?

Most of the big consolidations can wait. That includes migrating to one ERP, merging customer databases into one master, moving payroll to a single platform, retiring a second CRM, and restructuring email domains beyond what security needs. These are real projects, and they belong on the roadmap with an owner, a budget and a sequence, not on the first-100-days list.

Moving them early is how companies break things they did not know existed. What cannot wait is anything that protects cash and security: invoicing and payroll working, access cleaned up, backups proven, and contracts with notice dates ahead of you. Everything else earns its place on the roadmap by business value and risk, and sometimes the right answer is to run two systems on purpose, with an end date.

When do we exit a transition services agreement?

A transition services agreement, or TSA, is the contract under which a seller keeps providing systems and services to a carved-out business for a set period. Plan your exit from day one, because the clock is fixed and the seller's patience is not unlimited. For each service on the TSA, decide what replaces it, who builds it and when it must be live, then work backward from the end date to set the schedule.

Exit one service at a time, test the replacement in parallel before you cut over, and do not leave the hardest items to the last month. Ask early whether the seller will extend a service if you need it, and on what terms, in writing. The pro audio carve-out in our case study ran against a fixed deadline for 179 systems, which is why the plan comes before the work.

Who should lead it?

One accountable person who can make decisions across both companies and answer to the CEO or sponsor. The IT manager of either company is usually the wrong choice: they are busy keeping the lights on, and they have a stake in the outcome. For most companies this size, fractional CIO leadership fits better than a full-time hire, because the work is intense for a few months and then changes shape.

Common questions

Should you merge the two companies' systems right away?

Usually not. In the first 100 days the goal is to keep both businesses running, learn what you bought and decide where you are going. Large migrations rushed in the first weeks tend to break things you did not know existed.

What is the two of everything problem?

After a deal, you often own two ERPs, two CRMs, two sets of reports and two versions of the same customer. The cost is not only the duplicate licenses. It is the people re-keying data and the leadership team looking at numbers that do not agree.

Who should lead technology integration?

One accountable leader who answers to the CEO or deal sponsor and has authority across both companies. For most companies this size, a fractional CIO is a better fit than a full-time hire at this stage.

What are quick wins in the first 100 days?

Cutting duplicate or unused contracts, giving the owner one combined view of cash and revenue, fixing access and security gaps, and removing manual re-keying between the two companies where it is cheap to do so.

Not sure where to start?

Take a free three-minute score. If a conversation makes sense, it will offer one.