Check the notice trigger and commitment
Put the starting event beside every notice period. Notice before a renewal date, convenience termination during an active term and a reduction in purchased units can follow different rules. The examples below concern the named service and published document; the incorporated agreement, amendments and order still determine the actual purchase.
Benchmark365 / White-label help desk
- The FAQ advertises monthly-to-annual options. Public agreement clause 4.1 states a five-year initial term; clause 4.3 separately permits termination with notice and possible costs. Confirm the incorporated agreement version and Order Form before treating the service as a monthly commitment. Public agreement / 2026-10-17 (external website) Help desk FAQ / 2026-10-17 (external website)
- Clause 4.3 describes 30 days of written notice, counted from the end of the current billing cycle. Early termination costs may be set by the Order Form; the clause also provides for reasonable incurred costs less fees already paid. Public agreement / 2026-10-17 (external website)
Settle in the order: Which incorporated agreement and Order Form apply, when does the billing cycle end, and which costs remain if this helpdesk order is terminated?
Read Benchmark365 service details / Build an RFP for this service
IT By Design / Managed L1/L2 helpdesk
- Each SOW defines its own term under the applicable service Addendum. Unless the SOW says otherwise, renewal repeats the initial term and requires at least 90 days of written non-renewal notice. Obtain the signed service documents before treating any offer as month-to-month. MSA - July 2026 / 2026-11-06 (external website)
- The MSA default is at least 90 days of written notice before term expiry for non-renewal, unless the SOW provides otherwise. Mid-term convenience exit has separate restrictions and possible remaining fees, subject to the applicable Addendum or SOW. MSA - July 2026 / 2026-11-06 (external website)
Settle in the order: What are the initial term and expiry date in this SOW, which Addendum overrides the framework, and are you requesting non-renewal or early convenience exit?
Read IT By Design service details / Build an RFP for this service
Sherweb / Core NOC on Sherweb tools
- The published service schedule states a 12-month minimum from service commencement. Convenience termination before it ends leaves fees for the remaining minimum term payable. Confirm the incorporated schedule and order. NOC schedule / 2026-10-17 / PDF p. 2 (external website)
- Both service schedules make termination effective on the last day of the month after the month when notice is received. Minimum-term and remaining-fee conditions still apply. Reducing contracted units has separate notice thresholds. Helpdesk schedule / 2026-10-17 / PDF p. 2 (external website) NOC schedule / 2026-10-17 / PDF p. 2 (external website)
- The NOC offboarding section says agent removal, including endpoint protection, can take up to 30 days and supplies no offboarding report. Agree exports, replacement protection and removal sequence before the service ends. NOC SOW / 2026-10-17 / PDF p. 19 (external website)
Settle in the order: Which minimum-term fees and final effective date apply, and who accepts the queue, replacement protection and agent removal before the NOC handover is closed?
Read Sherweb service details / Build an RFP for this service
Keep the confirmed notice date, the end of paid commitments, intake handover, access removal and the last permitted data retrieval as separate milestones in your plan. A monthly invoice or a request to stop service does not by itself settle all five.
Assign the exit work
| Workstream | Evidence to obtain before purchase | Exit owner |
|---|---|---|
| Notice | Method, address, deadline and acknowledgement requirement | Contract owner |
| Charges | Committed licenses, minimums, overlap and exit fees | Finance and contract owner |
| Documents | Available formats, scope, deadlines and deletion terms | Operations/data owner |
| Queue | Outstanding incidents, accepting team and client updates | Service owner |
| Access | Accounts, tokens, delegated roles and tested revocation | Access owner |
| Continuity | Replacement coverage and reversible routing | Operations owner |
Assign each workstream to a person or accountable role in your own organization. It is not sufficient to write that the supplier will handle exit. Document which tasks require cooperation and which the MSP can execute independently.
Do not assume documents are exportable
Some services keep their own operational history. Others work in buyer-owned tools. Both models require a defined retention and handover path. See the Kaseya NOC profile for a concrete public-term example that makes export an important pre-purchase question. Follow the source and check negotiated amendments; do not generalize that term to another provider.
The Kaseya NOC terms (external website) retain tickets for six months after creation during a subscription and exclude customer export. The separate Help Desk terms (external website) provide one-year ticket retention and PSA access, while call recordings have restricted release. These are different data paths, checked 6 November 2026. Agree how your own systems will retain decisions, open work and handover notes from the start.
A retention duration does not settle your right to retrieve information after service termination. Obtain the last permitted retrieval date, the accessible formats and the delivery method for your own handover copy.
LTVplus / access to working materials
Provider-created training and process materials remain LTVplus intellectual property under the public terms. A former client can request a read-only copy containing its proprietary inputs within 90 days, subject to identity checks. Agree usable runbook exports and rights before launch; personal-data rights are addressed separately. Public terms dated 13 August 2026 / 2026-10-18 (external website)
Settle before launch: Which materials will be editable, which will be read-only, and how will you request the permitted copy before the 90-day window closes? Agree formats, access after account closure and any separate handover work.
Read LTVplus operating terms / Build an RFP for this service
Inputiv / return, retention and export windows
Section 14.4 describes return or secure destruction of confidential information within 14 days, subject to legally required retention. Section 14.5 allows a request for TBR Client Data export within 30 days after termination. Agree a usable export of helpdesk and project materials separately; the TBR window does not define every work product. Public terms updated 1 October 2025 / 2026-11-06 (external website)
Settle before launch: Which helpdesk and project materials will be delivered, when and in what usable format? Separate confidential-information return from TBR Client Data export, and identify any legally retained copy and its access controls.
Read Inputiv operating terms / Build an RFP for this service
Request a sample permitted export early. Verify ticket identifiers, timestamps, actions, attachments, ownership and whether the format can be read without the supplier's account. Where the agreement does not provide an export, decide whether buyer-owned documents and agreed reports are sufficient for continuity before enrollment. Do not rely on a promised future exception.
Sequence the handover
First reconcile outstanding work and agree the final acceptance point. Assign new intake to the replacement team, then obtain explicit acceptance of existing incidents. Revoke access according to the agreed transition window while preserving an authorized continuity route. Rotate shared secrets where needed and verify that delegated access and service integrations have actually stopped. Keep proof of notice and completed revocation.
Illustrative handover acceptance: the replacement team accepts incident EX02 with its action history, next update deadline and named owner; the previous provider confirms it will take no further action after the agreed time. This is a hypothetical example, not a completed provider exit.
Check each path of access
Named people and application sessions
For named Entra users, agree both sign-in removal and how sessions in each downstream application end. Microsoft explains that an application's own session cookie follows that application's controls. Refresh-token revocation alone is not universal proof that every session has ended.
Before accepting: Ask for the affected identity, application owner, approved action, actual completion time and an authorized check of the old access path.
Delegated partner administration
Identify the exact customer, partner and GDAP relationship. Microsoft's customer-led process removes the administration granted through that relationship. Its FAQ separately explains that ending GDAP does not end the reseller relationship; settle subscription and commercial work independently.
Before accepting: Obtain the relationship confirmation and an authorized check of the agreed administrative scope. List any separately granted access that still needs its own owner and action.
Enterprise application permissions
List each enterprise application or service principal and whether it uses delegated or application permissions. Microsoft treats these grants, user/group assignments and other authorization systems separately. Removing a current grant also does not, by itself, prevent a later consent grant.
Before accepting: Ask the application owner to document the agreed permission change, remaining roles, consent controls and a permitted check of the old integration. Keep the replacement integration assigned to its own owner.
RMM, PSA and other service access
For your own systems, separately inventory RMM agents, remote-access accounts, PSA API users, service identities and vault entries used for this purchase. Ask each system owner how the old provider will stop acting while the replacement keeps the agreed coverage.
Before accepting: Agree the tool or agent owner, intended scope, action-stop time, approved disable or rotation step, old-path access check and replacement monitoring check. Keep an unverified path open in the plan.
These are proposed checks for your authorized team. Agree the sequence and receiving coverage before changing live access. The identity-verification guide covers recovery requests; the integration guide helps define the ticket workflow that remains.
Use the blank access log alongside the six-workstream exit log below. It keeps each old access path, replacement owner and unanswered check separate.
Close operational and financial work separately
Stopping access does not necessarily end contractual charges. Reconcile the final enrolled inventory, committed units, disputed items and any return/deletion confirmation. Assign unresolved disputes without holding operational continuity hostage. Keep your legal retention requirements distinct from a supplier's deletion promise. Use the transition plan, RFP and pricing normalization to settle these requirements while you still have a choice of suppliers.
Blank exit log
Keep notice, queue acceptance, permitted exports and access confirmation together; close financial obligations separately.
Use Word for an editable working copy with space for owners, observations and decisions, or open Markdown in a text editor. Both contain the same blank log. All review and acceptance states start unanswered.