---
title: "Fullcast plan cutover go-live run list"
slug: "fullcast-plan-cutover-go-live-run-list"
description: "A step by step checklist to coordinate tasks for a seamless transition of territory coverage and account team member assignments between Fullcast and Salesforce when you cutover or switch to a new plan."
tags: ["Export", "Salesforce Admin", "Tenant Admin"]
updated: 2026-02-24T20:05:04Z
published: 2026-02-24T20:05:04Z
canonical: "support.fullcast.com/fullcast-plan-cutover-go-live-run-list"
---

> ## 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.

# Fullcast plan cutover go-live run list

When you cut over from your current Fullcast GTM Plan to the new fiscal year plan (switch from one exporting plan to a new one) coordinate tasks and actions between Fullcast and Salesforce to ensure a seamless transition of territory coverage and account team member assignments into Salesforce with minimal disruption to daily operations.

> [!NOTE]
> Note
> 
> Download a copy of [the worksheet](https://docs.google.com/spreadsheets/d/1A9mDpxMwZFDxPKt3FpKJVmoPh211IlSiLL4DFoIS450/edit?usp=sharing) to manually track progress.

## Phase 1: prepare and validate

Ensure data integrity, and run simulations to identify potential issues before the live cutover.

**Timing:** One month prior to the cutover date.

### Fullcast actions

| Action | Details | Impact |
| --- | --- | --- |
| [Mass update](/v1/docs/mass-update-assignments) assignment end dates on current exporting plan. | To prevent any lapses in coverage, confirm that all current assignment end dates align with the planned cutover date. | Prevents accounts from becoming unassigned if the cutover is delayed. |
| Validate [policies](/v1/docs/editing-policies)have been created | Review the active policies in the current plan and ensure all necessary policies (Holdout, Assignment) have been replicated or updated in the new plan. | Ensures proper assignment logic is maintained after the cutover. |
| Commit all changes in new plan | Ensure that all recent changes in the new plan are committed to the database and ready to be pushed to Salesforce. | Guarantees that the latest, approved plan is used for the export. |
| Validate [territory coverage](/v1/docs/viewing-coverage-and-capacity) assignments in your new plan. | Review which roles have been assigned for coverage. Note which roles need to be exported. Ensure all territories have the intended coverage. | Eliminates territory coverage gaps post-cutover. |
| Compare [plan settings](/v1/docs/configure-plan-settings) | Review and confirm the following settings in the new plan match expectations: plan-level data filters, auto rerun rules settings, and roles enabled for export. | Ensures the export scope and automation rules are correctly defined for the new plan. |
| [Run a simulate export](/v1/docs/simulate-an-export-job) (**Migrate All**) | Run a final simulation of the **Migrate All** export job. | Provides a final report on all records that will be upserted and deleted, allowing for pre-cutover troubleshooting. |

### Salesforce actions

| **Action** | Details | Impact |
| --- | --- | --- |
| Review original go-live notes | Ensure the Salesforce team is fully involved and prepared for the cutover, understand the specific impact on your org, automations, etc. | Facilitates seamless coordination and adds organization-specific items to the run list. |
| Align stakeholders | Confirm the cutover date and time with all relevant sales, operations, and IT teams. | Reduces operational surprises and allows teams to plan for minimal system downtime. |

## Phase 2: lock down and execute

Temporarily lockdown Salesforce and execute of the main cutover job in Fullcast.

**Timing:** On the day of the cutover date.

### Salesforce actions

| Action | Details | Impact |
| --- | --- | --- |
| Backup account data | Perform a final, recent backup of critical account ownership and assignment data. | Provides a safety net in case of unforeseen data issues during the cutover. |
| Lock down account moves | Disable or remove permissions for end-users to manually move accounts or change account ownership. | Prevents users from manually overriding assignments while the system is transitioning. |
| Disable Fullcast [change owner lightning action](/v1/docs/configure-the-change-owner-action-in-salesforce#add-the-change-owner-button-to-account-layout-in-salesforce) | Deactivate the quick action that allows for manual changes to account owner. | Ensures assignment integrity during the cutover. |
| Disable routing flows | Temporarily disable all Salesforce flows related to Fullcast routing. | Prevents new leads or accounts from being incorrectly routed by the old logic during the data transition. No records will be routed during this period. |
| Disable notifications or other downstream actions triggered by Fullcast export | Review and temporarily disable certain downstream aspects of account owner changes, such as notifications | Reduces unnecessary processing load and flow failures during the large Migrate All job. |
| Turn off other scheduled jobs | If possible, turn off any non-essential scheduled batch jobs or nightly processes. | Minimizes system load and potential interference with the Fullcast export job. |

### Fullcast actions

| Action | Details | Impact |
| --- | --- | --- |
| [Disable policies](/v1/docs/activating-and-deactivating-policies) (old plan) | Deactivate all policies within the previous plan. | Ensures the old logic is completely dormant and cannot conflict with the new plan's logic. |
| [Disable roles](/plan-and-pay/docs/viewing-and-managing-roles#manage-existing-roles) (old plan) | Deactivate all roles within the previous plan. | Nothing happens immediately; the last export state remains in Salesforce and Ensures that the old plan is isolated. |
| [Disable old plan for export](/v1/docs/configure-plan-settings) | Deactivate the current year's plan export setting. | Nothing happens immediately; the last exported state remains in Salesforce. This isolates the old plan. |
| [Enable new plan for export](/v1/docs/manage-export-jobs#enable-a-plan-for-export-in-fullcast) (new plan) | Activate the export setting on the new fiscal year plan. | This triggers the system to recognize the new plan as the official source of truth, but does not kick off an immediate export job. |
| [Enable roles for export](/v1/docs/viewing-and-managing-roles) | Confirm which specific roles (SDR, AE) will be included in the Account Team Member export. | Defines the exact scope of assignments being pushed to Salesforce. |
| [Run ad hoc export](/v1/docs/manage-export-jobs#run-an-adhoc-import-or-export-in-fullcast) — migrate all | Execute the **Migrate All** job. | This critical step pushes the new GTM Plan Object and, most importantly, executes the appropriate cleanup and upserting of Account Team Member records in Salesforce. |
| [Enable new plan policies](/plan-and-pay/docs/activating-and-deactivating-policies) | Enable all policies within the new plan. | Ensures the new logic is active and completes the new plan's logic. |

## Phase 3: re-activate and monitor

Ensure the new plan is fully operational and the system is returned to normal automation status.

**Timing:** On the day of the cutover date.

### Fullcast actions

| Action | Details | Impact |
| --- | --- | --- |
| [Monitor job status](/v1/docs/review-job-status) | Track the export job progress in Fullcast, including the number of records processed at each stage. | Allows for real-time identification and mitigation of any system-side failures. |
| [Enable routing policies](/v1/docs/activating-and-deactivating-policies) (Only after export completes successfully) | Re-activate the policies in the new plan that govern assignment logic (e.g., assignment rules, holdout policies). | Ensures assignment logic is live for inbound records. |
| [Set up export schedule](/v1/docs/configure-a-scheduled-job-in-salesforce) (Only after export completes successfully) | Configure the recurring export schedule (e.g., nightly) for the new plan. | Establishes the automation needed for ongoing maintenance and updates. |

### Salesforce actions

| Action | Details | Impact |
| --- | --- | --- |
| Troubleshoot job issues | Review the job log and troubleshoot any common issues, which often stem from Salesforce permission or configuration issues during plan cutovers. | Essential for successful completion of the initial **Migrate All** job. |
| Enable flows related to export (Only after export completes successfully) | Re-activate the Salesforce flows that are triggered by the Fullcast export (for reporting or downstream processes). | Restores full system automation. |
| Enable routing policies and flows (Only after export completes successfully) | Re-activate all routing policies and associated flows that were disabled during the lockdown. | Restores automated lead/account routing to the newly assigned owners. |
| [Enable change owner lightning action](/v1/docs/configure-the-change-owner-action-in-salesforce) | Re-activate the list or page view buttons for the Fullcast change owner action. | Ensures the button is available for relevant users. |

**Go-to-market:**The strategy used to bring a product to market.