--- title: "Check cutover readiness with the Fullcast MCP" slug: "check-cutover-readiness-with-the-fullcast-mcp" description: "Use Fullcast’s cutover readiness skill in Claude to check plans, coverage, policies, exports, and Salesforce tasks before or after go-live." tags: ["cutover", "skills", "AI", "MCP"] status: "update" updated: 2026-11-19T15:00:14Z published: 2026-11-19T15:00:14Z canonical: "support.fullcast.com/check-cutover-readiness-with-the-fullcast-mcp" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.fullcast.com/llms.txt > Use this file to discover all available pages before exploring further. # Check cutover readiness with the Fullcast MCP > [!NOTE] > Early access feature > > This feature is currently available for early access. Contact your CSM for more information. Run the cutover readiness skill to see whether a Fullcast plan is ready to export to Salesforce, with a dated list of what's left. Run it a month before a go-live, cutover, or plan extension, and again the day before. You can also run it after a cutover to confirm all tasks are complete. ## Before you begin - The Fullcast MCP must be connected to Claude. For steps, refer to [Set up the model context protocol (MCP)](/plan-and-pay/docs/set-up-the-model-context-protocol-mcp). - You need permission to view plans, territories, coverage assignments, and policies in Fullcast. - Optional: You need Tenant Admin, Sys Admin, or a Reporting role for the skill to check your recent import and export jobs. ## Add the cutover readiness skill to Claude The skill is a zip file you can get from your CSM. You add it to Claude once, and Claude loads it whenever you ask about cutover or go-live readiness. 1. Obtain [**fullcast-territory-planning.zip**](http://fullcast-cutover-readiness.zip). 2. In Claude, go to **Customize.** 3. In the **Skills** section, click **Add** and select **Upload a skill**. 4. Select the .zip file. Do not unzip it first. 5. Confirm the skill shows in your list and is turned on. ## What the readiness check covers The skill is read-only. It looks at your Fullcast data, asks you about the Salesforce steps it can't see, and tells you what to fix. It never commits, moves, or changes anything. You make the fixes yourself. It works out which of three paths you're on and confirms it with you: | Path | When it applies | What it focuses on | | --- | --- | --- | | First go-live | No plan exports to Salesforce yet. | Salesforce connection, accounts and people loaded, coverage on the go-live date, and manually created Account Team records that will collide with the first export. | | Plan-to-plan cutover | One plan exports today and you're switching to a new plan, usually for a new fiscal year. | Which plans export, uncommitted changes, coverage on both plans, policies carried over, and recent export errors. | | Extend | You're keeping the current exporting plan for the next fiscal year. | Assignments that end on the last day of the fiscal year, so coverage doesn't go dark on day one. | Depending on the path, the skill checks the following. ### Plans and policies - More than one plan set to export, or none. - Uncommitted territory changes. Uncommitted changes don't export, and a simulate export only reflects committed data. - Active routing or holdout policies in the old plan with no match in the new plan. ### Coverage and people - Export roles missing from the new plan, or new roles that may clash with Account Team records someone added in Salesforce by hand. - Coverage on the old plan that lapses before the cutover date, or within 30 days after it if the cutover slips. - Coverage gaps on the new plan on the cutover date. To-be-hired (TBH), to-be-replaced (TBR), and to-be-transferred (TBT) placeholders count as gaps. - Assignments that start after the cutover date or end before it. - Assigned people who are inactive in Salesforce or offboarded in Fullcast. Salesforce rejects Account Team records for inactive users. - Accounts sitting in Unassigned nodes. ### Export health - Export errors in the last 30 days, grouped by likely cause. - Active Fullcast incidents or scheduled maintenance on the cutover date. The skill can't see your Salesforce org or which roles are turned on for export in plan settings. It asks you about those instead. For the full list of Salesforce and Fullcast tasks, refer to [Fullcast plan cutover go-live run list](/plan-and-pay/docs/fullcast-plan-cutover-go-live-run-list). ## Run a readiness check 1. In Claude, start a new chat. 2. Ask for a readiness check in your own words, for example: `Are we ready for cutover on Feb 1?` or `Check my new plan before we export.` 3. Confirm the path and answer the setup questions. The skill asks only what it can't work out: the plan going live, the cutover date, which roles go to Salesforce Account Teams, and whether you're checking before or after the cutover. If you don't name a date, it uses the first day of your next fiscal year. 4. Answer the Salesforce checklist. The skill sends one numbered list covering items such as integration user delete access, flows to pause, backups, and simulate export results. Reply with the numbers that are done. Any item you don't answer stays **Unconfirmed**, and an Unconfirmed item due on or before today makes the verdict **Not ready**. ## Read the readiness report The report opens with a one-line verdict: | Verdict | What it means | | --- | --- | | **Not ready** | At least one blocker, or at least one Salesforce item due today or earlier is still unconfirmed. | | **Ready with warnings** | No blockers, but there are warnings to review. | | **Ready** | Nothing open. | Below the verdict: - **Blockers** and **Warnings**: what's wrong, what happens on cutover day if you ignore it, where to fix it, and a link to the support article. Checks the skill couldn't run, such as job history without an admin role, show up as warnings with the reason. - **Not confirmed yet**: Salesforce-side items you haven't confirmed, with due dates. - **Run list**: a dated table from today to your cutover date, built from one month prior, one day prior, and day-of timing. Past-due items are marked overdue. - A count of passed checks. Ask to see them if you want the detail. The run list **Status** column uses these markers: | Marker | Meaning | | --- | --- | | ✅ | Passed or done. | | ⚠️ | Warning. | | ❌ | Blocker or overdue, even if it isn't due yet. | | — | Not due yet, or the skill can't check it. | ## Fix an issue and check again 1. Fix the blocker or warning in Fullcast or Salesforce using the linked article. 2. In the same chat, ask the skill to run that check again, for example: `Re-run the coverage check.` To share the report with your team, ask the skill to save it as a document. ## Verify a cutover after it runs After your cutover export finishes, ask `Did the cutover work?` The skill checks that: - Only the new plan is set to export. - The most recent export job finished without errors. This check needs an admin role. - Routing and holdout policies are active in the new plan and inactive in the old plan. A policy type active in both plans, or in neither, is a blocker. - Coverage on the new plan holds as of today. It then asks you to confirm the export schedule is set on the new plan, Salesforce flows and the change owner action are back on, and spot-checked accounts look right in Salesforce. For the full post-cutover checklist, refer to [Best practices for executing fiscal year cutovers](/plan-and-pay/docs/best-practices-for-executing-fiscal-year-cutovers). ## Share feedback on the skill The cutover readiness skill is in beta. If a check flagged something that shouldn't be a blocker, or missed something you expected, tell your Customer Success Manager (CSM) what you asked and what the report said. ## Related - [Fullcast MCP tool reference](/fullcast-mcp-tool-reference.md) - [Set up the model context protocol (MCP)](/set-up-the-model-context-protocol-mcp.md) - [Set up your AI client for Fullcast](/set-up-your-ai-client-for-fullcast.md)