Export process

The export of GTM plans from Fullcast to Salesforce is impacted by several settings in Fullcast, including:

If a plan is enabled for export
Which roles are enabled for export

Refer to integration between Fullcast and Salesforce for more about Fullcast’s custom objects.

Changes made in Fullcast must be committed to be picked up and executed in the next export job.
Salesforce does not reflect assignment updates made after a successful export.

Note
The export process is the same for all standard integrations. Custom jobs function differently.

Process overview

When you export your go-to-market plans (territory, team, and product plans) from Fullcast to Salesforce, the job executes as follows:

The process for exporting a GTM plan.

Initiate export: Run an export job in Fullcast ad hoc or create a scheduled job. Jobs can be full or partial—for partial exports, specific actions trigger a record to be included in an export job.
Run cleanup job: The cleanup job removes orphaned records, such as account team members associated with coverage assignments that have ended. Various actions can trigger a record to be included in cleanup.
Update Fullcast GTM object: This creates or updates Fullcast GTM records, which are the primary object representing your plan hierarchy nodes within Salesforce.
Update Fullcast member objects: This includes team member, territory member, and product group member records.
Update Account Team Members: Territory coverage assignments are exported to account team member records.
Export complete: Throughout the export job, the status can be monitored in Fullcast’s Jobs setting tab.

Export triggers

For export jobs that are set to migrate latest, below are the objects and associated changes that can trigger a record to be created or updated in Salesforce (for export jobs that are set to Migrate all, all records are exported.)

Object	Export triggers
Fullcast GTM	A node is created from a territory, team, or product plan that is enabled for export. A node expression is modified, such as when a territory rule is edited.
Territory Member Team Member Product Group Member	A record is created. A record moves to a different node and is committed.
Account Team Member	A territory coverage assignment is created or edited. A territory coverage assignment's start date has become active since the last export. A role is enabled for export. A plan is enabled for export. An account is moved to a different territory node.

Object

Export triggers

Fullcast GTM

A node is created from a territory, team, or product plan that is enabled for export.
A node expression is modified, such as when a territory rule is edited.

Territory Member

Team Member

Product Group Member

A record is created.
A record moves to a different node and is committed.

Account Team Member

A territory coverage assignment is created or edited.
A territory coverage assignment's start date has become active since the last export.
A role is enabled for export.
A plan is enabled for export.
An account is moved to a different territory node.

Cleanup triggers

The cleanup job ensures that records in Salesforce accurately reflect the current state of your Fullcast GTM plan. When records are removed or changed in Fullcast, this process triggers a deletion of the corresponding records in Salesforce. The following table details the specific events that trigger a deletion.

Object	Deletion triggers
Fullcast GTM	A node (territories, team, or product) is deleted. The plan export is turned off.
Territory Member Team Member Product Group Member	The record is deleted in Salesforce, which then gets deleted from Fullcast. The record moves between nodes and is committed in a new node. The plan export is turned off.
Account Team Member	A territory coverage assignment is deleted. A territory coverage assignment becomes inactive because its end date is today or in the past. The User assigned to the assignment becomes inactive. You delete the node where an account exists. You move an account from one node to another. You disable export for a role.