Client tries to reverse cancellation during offboarding
When a departing client attempts to reverse their cancellation late in the transition period, it creates immediate legal, liability, and operational confusion. Managed service providers face the dilemma of halting a handover already in progress or trying to restart a relationship where documentation and access credentials may have already been signed over.
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.
- 1Charging a reinstatement invoice and requiring a paid onboarding process or price hikeDid this help you?
- 2Refusing a handover period or refusing to hand over passwords until the absolute final day of serviceDid this help you?
- 3Enforcing strict 90-day termination notice periods and billing all offboarding strictly on a time and materials basisDid this help you?
- 4Hoarding money to inflate the emergency fundDid this help you?
- 5Accelerating plans to build a private practice on the sideDid this help you?
- 6Evaluating worker classification with the Department of Labor or a labor attorneyDid this help you?
- 7Rotating everything manually or disabling SSODid this help you?
- 8Relying on tribal knowledge and ad-hoc checklistsDid this help you?
- 9Slowly revoking access over the course of 3 monthsDid this help you?
- 10Exporting database rows and spinning up a new instanceDid 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.
“Towards the end of June I received a termination email from a client, and they had decided to move to this same dumpster fire.”source ↗
“On day 58, the PoC emails me and says that despite good recommendations, they're not feeling confident in the new provider and that they need more time to either stay or transition.”source ↗
“For that scenario you mention, once I hand over documentation and passwords, my contract, liability, and any duty to help the customer ends.”source ↗
“previous sysadmin was using fortitoken, when he left, he uninstalled the app without handing over anything, i had to reset fortigate and rewrite a new config”source ↗
“You didnt implement good security from the get go and dont want to dedicate someone...what do you think is needed at this point?”source ↗
“When a dev or contractor leaves, there are SSH keys in authorized_keys on a dozen boxes, a DB password everyone knew, staging .env files in Slack DMs, maybe AWS keys on their laptop.”source ↗
“So I’m currently working at a 1099 with plans to slowly branch out into my own practice on the side.”source ↗
“Reason I fear a layoff is essentially suspicious activity going on at the place I work for. Prominent employees are getting dropped and corporate is starting to enforce practices that hurt income of the employees.”source ↗
“So as a 1099, there’s no severance, no 401k, and likely no heads up past when they feel like it.”source ↗
Where this came up
People with this problem also raised
- 7How to quickly revoke all access for a terminated employee
- 5How to catch all account dependencies during user offboarding
- 6Why is it so hard to cancel digital subscriptions?
- 2How to escape dead-end accounts payable contracts
- 3Canceling a service agreement accepted by email
- 4How to track service retirements across multiple client tenants