When an MSP relationship ends, your data does not always come back automatically, in a usable format, for free, or on a defined timeline. Whether it does depends entirely on what your contract actually says about exit — and a surprising number of published agreements say nothing at all.
The three things to check for
Search your agreement's termination or "effect of termination" section for whether it states, explicitly:
- An affirmative obligation to return or export your data — not just a general statement that the provider will "cooperate" with an exit.
- A format — is the data returned in a usable, exportable form, or only as a static export that may not be importable anywhere else?
- A deadline — a specific number of days after termination by which the data must be returned, not an open-ended "reasonable time."
Some published contracts include all three, stated as a clear obligation with a format and a deadline attached. Others contain no affirmative obligation to return or export data at all — the contract is simply silent on it, which in practice means you are negotiating from a weaker position at the exact moment your relationship with the provider is ending.
The off-boarding charge that often isn't priced in advance
Even where a data-return obligation exists, check whether exit assistance and data export are billed as a separate project at the provider's rates in effect at the time — with no ceiling and no advance quote stated in the contract. One published industry template describes exit assistance as something that "may trigger a billable project ... billed at Provider's then-prevailing rates," which means the actual cost of getting your own data back is not knowable when you sign, and may not be knowable until you are already mid-exit and have limited leverage to negotiate it.
This is a distinct issue from the early-termination fee covered in our red flags guide — a contract can charge both a termination fee for ending early and a separate, uncapped off-boarding charge for the data-return process itself.
Amounts already paid are usually not refunded
Check the termination section for language about fees already paid for a period after the termination date. A common pattern: amounts paid in advance for service after termination are not returned, even though the service will not be delivered for that period. This is worth knowing before you time a termination near the start of a billing period rather than the end of one.
What to ask for instead, before you sign
If your current contract is silent on data return, or leaves the format, deadline, or price open, these are reasonable things to ask a prospective or renewing provider to add in writing:
- A specific number of business days after termination by which a full data export must be delivered.
- A named, standard, non-proprietary export format (or at minimum, a format your next provider can actually import).
- A stated cap, or a specific pre-agreed rate, for any off-boarding or transition work — not open-ended "then-current rates."
- Confirmation of what happens to backups and any data held by a subcontracted third party, not just data on the primary provider's own systems.
If you are already mid-contract and the agreement is silent on these points, that silence is itself useful information: it tells you to start the conversation with your provider well before you actually need to leave, not during the transition itself.
Backups, subcontractors, and where your data actually lives
A data-return clause that only addresses the provider's primary systems can miss data held elsewhere — backups kept by the provider on a separate retention schedule, and data processed or stored by a subcontracted third party (a backup vendor, a security monitoring service, a cloud host billed through the MSP rather than directly). Ask specifically what happens to each of these on exit, not just to the data on the systems you interact with day to day. A provider that commits to returning your primary data promptly can still be retaining backup copies for months under a separate policy that the termination clause never mentions.
Timing your exit around the data-return terms
Once you know what your contract actually promises — or does not promise — about data return, that knowledge should shape when and how you time an exit, not just whether you decide to leave. If off-boarding is billed at undisclosed rates and the contract gives no deadline, plan for a longer, more expensive, and less predictable transition than if the contract states a fixed number of days and a named format. Building that into your timeline — rather than discovering it after you have already given notice — is the difference between an orderly transition and a scramble.
Why this matters more than it seems like it should
Data return sounds like a minor operational detail next to a headline liability cap or a termination fee, but for many small businesses it is the single most disruptive part of switching providers. Email, client records, accounting integrations, and configuration details for every device on a network do not move themselves — someone has to export them, in a format the next provider can actually use, on a timeline that does not leave a gap in coverage. A contract that leaves this process undefined is effectively asking you to negotiate the terms of your own exit from a position of urgency, at the exact moment you have the least leverage: you have already decided to leave, the relationship is ending, and the provider holding your data has limited incentive to make the process fast or cheap.
A short example of what a clear clause looks like
A data-return clause that actually protects you tends to read close to this shape: "Within [a stated number of] business days of termination, Provider will deliver to Client a complete export of Client's data in [a named, non-proprietary format], at no additional charge beyond then-current fees already due." Compare that structure — a deadline, a format, and a stated cost (zero, or a disclosed cap) — against your own contract's language. If any of those three elements is missing, that is precisely the gap to raise before you sign a new agreement, or to flag now if you are already several years into an existing one and have never had reason to read this section closely.
Find out what your contract actually promises
TermSentinel checks an uploaded agreement for an affirmative data-return obligation, its format and deadline (or the absence of one), and how off-boarding work is priced, quoting the source text for each finding.