Offboarding and Transition

A controlled operational transition when services end or responsibility moves to another provider.

Service Guide Version: 2026-07-11

Offboarding confirms authority and timing, identifies receiving contacts, prepares available client-owned records, coordinates access and vendors, removes Cloud Core MSP tools and permissions, and documents completion and remaining dependencies.

Confirm the transition

Cloud Core MSP confirms the authorized transition request, affected services, responsible client contact, receiving provider or internal contact, requested timing, communication path, and known operational priorities. Contractual timing, fees, and rights are governed by the signed agreement.

  • Confirm who is authorized to approve access, exports, vendor contact, cutover steps, and service changes.
  • Identify the receiving technical contacts and the systems, sites, vendors, and services included in the transition.
  • Agree on a working schedule for information exchange, access changes, provider meetings, service cutover, and tool removal.
  • Identify dependencies that require client, incoming-provider, carrier, software-vendor, facility, or platform action.

Prepare documentation and data

Cloud Core MSP prepares client-owned environment documentation and supported data exports that are available through the systems it manages. Information is provided in available standard formats; compatibility with another provider's tools and completeness beyond the available client records are not guaranteed.

  • Provide current client-specific inventories, network information, vendor contacts, licensing references, support procedures, and other maintained environment documentation.
  • Assist with supported exports from cloud, backup, voice, monitoring, or other managed systems where the platform permits an export.
  • Identify records, settings, or exports that remain controlled by a software vendor, carrier, distributor, or other provider.
  • Record open issues, active vendor requests, scheduled changes, and known dependencies relevant to the transition.

Coordinate access and vendors

  • Transfer or update authorized administrative access, credentials, MFA, emergency access, domains, tenant roles, licensing portals, backup access, and vendor portals in a controlled sequence.
  • Coordinate incoming-provider meetings, knowledge transfer, account ownership changes, and approved access requests.
  • Work with supported internet, phone, cloud, software, licensing, and other vendors on authorized responsibility changes.
  • Confirm who will hold administrative responsibility after each access change and identify any vendor action still pending.

Remove tools and permissions

  • Schedule removal or transfer of Cloud Core MSP management, monitoring, security, backup, remote-access, voice, and support tools as applicable to the departing service.
  • Coordinate replacement coverage with the client or receiving provider before removing tools that affect monitoring, security visibility, backup status, support access, or service administration.
  • Remove Cloud Core MSP accounts, permissions, delegated roles, and remote access after the approved responsibility transfer.
  • Document tools or licenses that a vendor or receiving provider must replace, reassign, or reconfigure.

Confirm completion

Cloud Core MSP records the documentation and exports provided, access and vendor actions completed, tools and permissions removed, open dependencies, and responsibilities remaining with the client, receiving provider, or another vendor. Transition timing depends on authorized contacts, system access, vendor response, platform export functions, replacement services, and the approved sequence, so uninterrupted transition cannot be guaranteed.

Discuss the support your organization needs.

A 15-minute call will clarify your priorities, current responsibilities, and the appropriate next step.