M&A tech stacks

Day 1, Day 30 and Day 100 tech integration plan after an acquisition

Integration goes wrong when everything is urgent. Split the work into three checkpoints: keep the business running on Day 1, make the decisions by Day 30, and complete the moves by Day 100.

Short answer

A good integration plan has three checkpoints. On Day 1 people can log in, email and payroll work and customers notice nothing. By Day 30 the inventory is complete and each system has a decision: keep, merge, bridge or retire. By Day 100 the highest-value moves are done and the rest has a dated plan. The checkpoints are conventions, not promises about how long a given merger takes.

  • Google Workspace
  • Microsoft 365
  • Microsoft Teams
  • Slack
  • Salesforce
  • HubSpot
  • NetSuite
  • Make

Last reviewed . General planning guidance, not legal, tax or accounting advice.

The plan at each checkpoint

Day 1, Day 30 and Day 100 are common checkpoints, not promises about how long your merger will take.

Day 1

Nothing breaks, and everyone knows where to go

  • Confirm who can approve spend, access and system changes on both sides.
  • Freeze non-urgent changes to core systems.
  • Verify admin access to every core system and remove shared or former-staff access.
  • Keep both email systems running; add a shared directory or calendar sharing if needed.
  • Confirm payroll, billing and customer-facing systems run unchanged.
  • Publish one contact list and one channel for IT questions.
Day 30

A decision for every system

  • Finish the stack inventory with an owner for every system.
  • Mark each system keep, merge, bridge or retire, with the reason.
  • Choose the winner for each overlapping category and the owner of each migration.
  • List contract notice dates and set the order of negotiations.
  • Agree the identity plan: separate tenants with single sign-on, or one tenant.
  • Start the risk register and review it weekly.
Day 100

The high-value moves are done

  • Complete the identity and email moves agreed at Day 30.
  • Cut over the first merged system and confirm users are on it.
  • Run the CRM and finance consolidation to the agreed scope or bridge them with a documented sync.
  • Give leadership one reporting view across both companies.
  • Retire the first duplicate systems after archiving their data.
  • Publish a dated plan for everything not yet finished.

Tasks in each checkpoint of the plan below

Counted from the task lists on this page.

Show as table
ItemTasks in each checkpoint of the plan below
Day 16
Day 306
Day 1006

Where the numbers come from

These counts come straight from the lists on this page.

What has to work on Day 1?

Only the things customers and employees would notice: logins, email, payroll, billing and the systems that take orders. Resist the urge to change anything else.

  • Access: every core system has a verified admin, and shared passwords are replaced.
  • Communication: one place to ask IT questions and one named person who answers.
  • Continuity: both companies keep running on their own systems.
  • Safety: a freeze on non-urgent changes until the inventory is complete.

What should be settled by Day 30?

Decisions, not migrations. By Day 30 each system has a keep, merge, bridge or retire decision, a named owner and a reason, and the contract dates that drive timing are on one calendar.

  • Use the decision framework to avoid arguing system by system.
  • Pick winners on fit for the combined company, not on which side is the buyer.
  • Write down what you are choosing not to do yet, so it is a decision rather than an omission.

What does a realistic Day 100 look like?

The highest-value, lowest-risk moves are finished, leadership sees one report, and everything unfinished has an owner and a date. A complete merge of every system by Day 100 is usually not the goal.

  1. Close out the identity and email moves.
  2. Cut over one merged system end to end and learn from it.
  3. Retire the duplicates whose notice dates allow it.
  4. Review the risk register and update the plan for the next period.
FAQ

Questions on this topic

Are Day 30 and Day 100 fixed deadlines?

No. They are common checkpoints. Larger or regulated deals take longer, and some systems are deliberately bridged for much longer than 100 days.

Should everything move to the buyer's systems?

Not automatically. Choose the system that best fits the combined company. Sometimes that is the target's.

Who owns the integration plan?

One integration lead with authority over both IT teams, supported by a named owner per workstream.

Vendor documentation to check against

Product details change. Confirm current options in each vendor's own documentation. Consultants in a Box is an independent consultancy; this page is not published or endorsed by any vendor named. Names and logos are trademarks of their owners.

Merging two stacks?

Start with the free business analysis, or book a call and we will talk through both companies' systems and where to begin.

Book a free consultation

Tell us about your team and the software you need help with. We'll follow up to schedule a time to talk.

Open the form on its own page

Talk to a person

The fastest way is to pick a time. Prefer to write? Leave a message and we will email you back, usually the same business day.

Book a free call

By sending this you agree to our Terms and Privacy Policy.