Transfer in five gates
| Gate | Deliverable | Hold condition |
|---|---|---|
| Inventory | Clients, assets, users, coverage and exclusions | Counts or tenant mapping disagree |
| Knowledge | Approved runbooks, owners and escalation paths | Missing instructions for a critical service |
| Shadow operation | Both teams observe the same cases | Actions or ticket history cannot be reconciled |
| Limited cutover | One bounded queue or client group transferred | Buyer cannot restore retained coverage |
| Accepted operation | Outcomes reviewed and residual risks assigned | Blocking pilot failure remains unresolved |
An inventory should identify unsupported assets as well as enrolled ones. Alongside the client list, document business-critical applications, vendor dependencies, maintenance windows and special approval rules. Reconcile the billable inventory separately from the operational inventory so the first invoice does not define the service by accident.
Agree the dates before the first shift
Put preparation completion, first staffed coverage, operational acceptance and first charge on separate lines in the order. For each, specify the starting event, required access or information, timezone, responsible approver and what happens if a prerequisite is late. A quote turnaround is not a launch schedule, and a billing trigger is not proof that overnight coverage has begun.
Keep business days, calendar days and weeks in the units the supplier states. Resolve different estimates in the proposal instead of averaging them into a promised date. Use the published examples below to ask about the exact service you intend to buy.
Benchmark365 / White-label help desk
- The agreement overview states a one-time onboarding fee without an amount and a deposit equal to one month of service. Subscription charges start at signup while provisioning and onboarding proceed. Public agreement / 2026-10-17 (external website)
- The agreement overview describes 15 business days for setup and local business hours for the first 30 days. This differs from the FAQ estimate of 15-30 days; settle milestones, billing start and the first overnight shift in the order. Public agreement / 2026-10-17 (external website) Help desk FAQ / 2026-10-17 (external website) NOC FAQ / 2026-10-17 (external website)
Ask in the proposal: Which event starts subscription billing, when is setup accepted, and what is the first staffed overnight shift? Put the fee, deposit, initial hours and each date in the order.
Read Benchmark365 service details / Build an RFP for this service
INOC / Managed / white-label NOC - configured scope
- The dedicated turnup page says a typical four to eight weeks, while the general FAQ says six to nine weeks. Obtain the current schedule and prerequisites for the purchased scope; neither range is a guaranteed go-live date. NOC turnup process / 2026-11-06 (external website) General FAQ / 2026-11-06 (external website)
- The pricing explainer describes a typical quote time of about a week, depending on availability of the required information. A one-business-day contact follow-up is not a completed proposal. Pricing explainer PDF / 2026-11-06 / PDF p. 9 (external website)
Ask in the proposal: What information and access must be complete before the quote and turnup clocks start? Separate proposal delivery, preparation, first staffed coverage and acceptance for the selected arrangement.
Sherweb / Core NOC on Sherweb tools
- Core NOC invoicing begins when servers are ready for release to the operations team. The preceding assessment may take up to two weeks after deployment and discovery. NOC SOW / 2026-10-17 / PDF p. 4 (external website)
Ask in the proposal: Who declares the servers ready for release, what must discovery establish first, and how are the first paid date and operational acceptance approved? Name the actual core NOC SKU.
Read Sherweb service details / Build an RFP for this service
Microbyte / White-label helpdesk - user or ticket basis
- The FAQ estimates roughly six weeks for a standard white-label setup, allowing time to learn services, systems and customers. Agree prerequisites and an acceptance date; this is an estimate. White-label service FAQ / 2026-10-18 (external website)
Ask in the proposal: Which access, documentation, open-ticket audit and training inputs must be complete for your setup estimate? Agree the first accepted shift and backlog owner separately.
Read Microbyte service details / Build an RFP for this service
LTVplus / Managed Tier 1-2 helpdesk - dedicated engineer seat
- The pricing timeline allocates one week to solution design, including an agreed fixed monthly quote. Confirm when that stage starts and which inputs it needs. The 30-minute scoping call is meeting length, not quote turnaround. MSP pricing and FAQ / 2026-10-18 (external website)
- The pricing timeline describes three to four weeks total to launch, including solution design and knowledge transfer. Service pages also describe about 30 days. Agree access, runbooks, staffing and acceptance prerequisites. MSP pricing and FAQ / 2026-10-18 (external website)
Ask in the proposal: When does solution design start, when is the fixed quote agreed, and when is the selected helpdesk actually staffed? Put the access, knowledge-transfer and acceptance conditions beside the three-to-four-week estimate.
Read LTVplus service details / Build an RFP for this service
Lessons from published handovers
These supplier-selected accounts describe particular help desk engagements and a network-service relaunch. Their service versions and operating settings differ. The final column turns each account into a question for your own cutover plan.
| Published account | What the account describes | Agree in your plan |
|---|---|---|
| Go Computers / Benchmark365 - read the case (external website) | Founder Jeremy Johnson describes preparing documentation and staying involved with early tickets while the external team learned client context. | Who remains available for the first tickets, who corrects a missing runbook and when that retained involvement can reduce? |
| Bulletproof Infotech / Benchmark365 - read the case (external website) | Sean Tindall and Devin Chamberlain describe an early-2022 move, introducing a small customer group to a virtual helpdesk while internal staff focused on other work. | Which clients and duties move first, how will you explain the change, and what sends unfinished work back to your team? |
| Cage Data / Helpt - read the case (external website) | In the earlier HelptFul engagement, CTO Dave Long describes telling clients before onboarding. The account also covers KB articles, customer-specific notes and a feedback loop. | Who communicates the new contact path, documents client exceptions and turns each accepted escalation into reusable instructions? |
| Adtran / INOC - read the case (external website) | INOC identifies George Faucher, Senior Director of Global Services, in a network-service relaunch involving clearer scope, structured requirements, onboarding and joint product training. | Who accepts the service definition and training readiness, and how will the two teams report and correct a quality issue? |
Each case describes an earlier engagement. The linked profiles show the dates when its source was checked. A case describes that engagement's work, while your order must state the current service, staffing, fees and commitments.
Use the current Benchmark365, Helpt and INOC profiles to choose the purchase separately. Carry the responsibilities into the blank cutover log and agree them with your supplier.
Make knowledge actionable
For each runbook, document the signal, checks, permitted action, approval requirement, stop condition and rollback owner. Assign a version and reviewer. Ask the external team to explain one procedure back to the buyer using a test case; a document upload without a demonstrated understanding is incomplete transfer.
During shadow operation, select one active actor and one observer. Two teams making simultaneous fixes can hide responsibility or introduce conflicting changes. Document who will communicate with the customer and which ticket system holds the authoritative incident history. Resolve differences in tenant names, severity and ticket states before live cutover.
Cut over one obligation
Illustrative scope: transfer only the approved overnight workstation queue for a small consenting client group, retaining infrastructure changes and security containment internally. Document the exact start time and timezone, incoming owner, fallback phone route and how unfinished tickets are accepted. This example is not a proposed universal client rollout size.
Rollback triggers can include a tenant mismatch, inability to contact the escalation owner, missing permitted-action controls or an unacceptable backlog. Agree who makes that decision, how new work returns to the MSP and how the provider stops actions. Test independent access revocation before the buyer relies on it during an incident.
Verify after acceptance
Review the first invoice against enrolled scope, sample ticket quality and reconcile the retained workload. Keep open items with owners and due dates. Repeat the relevant checks when staff, tools or the client inventory change. Prepare an exit plan before removing the former coverage. Use the NOC pilot and desk pilot for service-specific acceptance evidence.
Blank cutover log
Keep gate decisions, the receiving owner, open conditions and any rollback in one working copy.
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.