You can duplicate a plan, also called cloning a plan, to create a full working copy, then adjust it for a new planning cycle without rebuilding territories, teams, targets, and policies from scratch. This article covers what a duplicate includes, what it resets, and what to set up first in the new plan.
For quick answers rather than the full walkthrough, see the FAQs: Duplicated plans.
Before you begin
You need tenant administrator permissions to create or duplicate a plan.
How duplicating works
In Fullcast, "duplicate" and "clone" mean the same thing. When you duplicate, Fullcast creates a new plan and copies the source plan into it as a single operation.
There are no options to copy part of a plan. You cannot choose to bring over territories but not targets, or assignments but not quotas. A duplicate copies everything, and then you edit the copy. The copy is fully independent, so editing it never changes the source plan.
Duplicate a plan
From the Manage Plans screen, find the plan you want to copy.
On that plan's tile, click the three-dot menu.
Select Duplicate.
Enter a name and description for the new plan, then confirm.
Duplicating runs in the background. Fullcast refreshes the screen when the copy finishes. A large plan takes longer, so allow a few minutes.
What copies over
A duplicate brings the full structure of the source plan:
Territory / Team / Product Plan
Go-to-market (GTM) hierarchy for Territories, Teams, and Products, including every node and the rules that sort accounts, people, and products into them
Placements, meaning which accounts, people, and products sit in which nodes
Note
Both committed and proposed states carry over to the duplicated plan. Committed placements come across as committed. Proposed changes that were not yet committed come across as still proposed, so you commit them in the new plan.
One thing to know: committed placements are stamped with the clone date, so in the new plan they show as placed at clone time, not on their original dates.
Named accounts and named exceptions, since each is stored as a flag on the account's placement and carries over with it
Coverage assignments, including who is assigned to each node and role
Targets and quotas, with their distributions, overrides, and adjustments
Roles
Roles and role permissions, including ramp profiles
Productivity and seasonality profiles
Policies
Policies and routing rules
Industry taxonomy
Reports
Saved reports and dashboards, with their data filters
Other
Scenarios and capacity planning line items
Ideal Customer Profiles (ICP), if your plan uses them
What resets or does not copy
A few things are switched off or cleared on purpose. Check these first in the new plan.
Export is turned off. The new plan is not enabled for export, even if the source plan was, and role export settings are cleared as well. Nothing syncs to your customer relationship management (CRM) system until you turn export on deliberately. This keeps two plans from pushing conflicting data to the same records.
Auto rerun rules are cleared. The new plan starts with no auto rerun rules. If you rely on rules that re-propose account allocations as data changes, set them up again.
Dates and fiscal years do not change. A duplicate keeps the source plan's fiscal years and all target and assignment dates exactly as they were. Duplicating this year's plan for next year does not move any dates forward. You update them yourself.
The new plan is not your production plan. A duplicate is never set as the production or exporting plan automatically. You set that when you are ready to cut over.
Note
Application Settings, including audits, jobs, users, fields, and metrics, are shared across every plan, so they are not part of the copy and do not need redoing.
Set up your new plan
Work through these before you start designing:
Rename the plan so it is clear which cycle it belongs to.
Update fiscal years and dates on targets.
Update dates on coverage assignments to the new period.
Review targets and quotas against the new numbers.
Rebuild auto rerun rules, if you use them.
Make your structural edits to territories, teams, products, and taxonomy.
When you’re ready to cut over, simulate the export to confirm exactly what would go to your CRM. Finally, enable export and set the production plan only at cutover, once everything checks out.
Why a compensation plan might not copy
Compensation plans and calculated fields copy by matching role and rule names between the source plan and the new plan. A role or rule with a unique, consistent name maps cleanly. If you have renamed a role, or two roles share the same name, the match can fail and that compensation plan or calculated field may not carry over. Fullcast reports anything it could not copy so you can rebuild it.
If a compensation plan is missing after a duplicate, check for a name mismatch first.