The first 30 days after your client's acquisition email lands

Follow-up to: When your client gets acquired, it's time to lead

Our recent post, When your client gets acquired, it's time to lead, made the case for why MSPs should move first when a client gets acquired. The short version: don't wait to be told what the new setup looks like. Show up with a plan.

But what does that plan actually look like, week by week? Here's a likely path forward.

Week one: get in front of it

The natural reaction is to wait and see. Wait for the new parent company to explain what's happening. By the time the brief arrives, someone on the new side has already started building an email-based workaround.

That workaround becomes the default. And defaults are hard to undo.

The better move is to email the client in the first week: "We know ServiceNow is coming. We've got a plan for how your tickets keep flowing between our system and theirs. Can we walk you through it next week?"

That one email changes the framing. The MSP goes from passenger to pilot.

Week two: map the ticket flow

Before anyone touches an API, map the ticket flow on paper. Four questions need answers.

What triggers a ticket to move? Usually it's an assignment group. The client assigns a ticket to a group like "MSP Escalation" in their ServiceNow, and that triggers a corresponding ticket in your PSA.

What moves with it? At minimum: title, description, status, priority, and comments. Most MSPs also want attachments. Agree on this up front, not six weeks into a live sync.

What happens when the ticket closes? This is where email-based workarounds fall apart. Someone closes a ticket in one system, but the other system doesn't know. In a proper sync, closing on one side closes on the other. Resolution notes, closure codes, the lot. We covered why this matters in Ticket integration: knowing your options.

Who owns the configuration? If only one person understands the integration, you've built a single point of failure. The person who built the Power Automate flow leaves, and the integration leaves with them.

Week three: run a proof of concept

Don't wait for the client's new platform rollout to be finished. Most ITSM platforms have sandbox or dev instances. Get access to one and run a small proof of concept.

Five or ten tickets. Real ticket types, not test data. Run them through the full cycle: creation, status update, comment, attachment, closure. You can check platform compatibility here before you start.

What you're proving isn't just that the sync works. You're proving to the client that you've already solved the problem they haven't started thinking about yet.

Week four: present the plan, not the problem

By week four, walk into the meeting with three things.

A working demo. Not a slide deck. A live sync between their ITSM platform and your PSA, running on real ticket types, with field mappings configured.

A scope document. One page. What syncs, what doesn't, who administers it, what the ongoing cost is.

A commercial model. If the MSP absorbs the cost, say so. If it's a pass-through, say so. Either way, it's a known line item, not a surprise.

Present the integration as part of the transition plan, not a separate project. "You're rolling out ServiceNow. Here's how we keep your tickets flowing during and after the transition. It's already configured."

The alternative

MSPs who wait tend to end up in one of three positions. They lose the client entirely. They keep the client but eat the swivel tax, with the service desk spending half its day rekeying tickets. Or they build a custom integration that takes six months, costs tens of thousands, and depends on whichever engineer built it.

The MSP that moves first, maps the flow, runs a proof of concept, and presents a working plan in the first 30 days is the one that keeps the deal.

Support Fusion connects IT ticketing systems including ServiceNow, ConnectWise, Autotask, Jira, HaloPSA, Zendesk, and more. If you've got a client going through an acquisition, or you know one's coming, book a demo and we'll show you the sync running on your exact platform pairing. Takes about 15 minutes.