Said It Here

Handling hostile outgoing IT providers during migration

Outgoing IT providers often sabotage migrations out of anger at losing a client, withholding cooperation and resorting to personal insults or threats. This obstruction forces the incoming team to rely on legal intervention just to get basic cooperation, turning a routine transition into a hostile standstill.

Overview
People affected2 accounts across 1 forum
Workarounds found3 items attempted
Community agreement352 total upvotes

What people tried

Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.

Found another way around this?

Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.

  1. 1
    Having attorneys write formal letters to force cooperation
    Did this help you?
  2. 2
    Contacting the client to intervene and handle the outgoing provider
    Did this help you?
  3. 3
    Refusing to deal directly with the outgoing provider and forcing the client to manage them
    Did this help you?

In their words

Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.

r/msp2 people · September 2025

“I was promised this will be the ‘most difficult migration’ I have ever done. Not because of complexity. Because the competitor is upset they are losing this small 3 seat client.”source ↗

“In the short conversation, there were many names I was called. The nicest being ‘low-life thieving piece of sh!t’.”source ↗

IndysITDept · r/msp · 350 upvotes

“That clown show was the hardest migration because the asshole just refused to respond to anything related to the change - didn’t matter if from customer or us. Ended up being hostile as attorneys had to write letters.”source ↗

RaNdomMSPPro · r/msp · 7 upvotes

Where this came up

People with this problem also raised