Migrate from FastTrack to Salesforce Sales Cloud

FastTrack Contact maps directly to Salesforce Contact. Most FastTrack contacts have a primary company link — we resolve that as AccountId after Account records are created. Unmatched company links surface as a pre-migration cleanup task; your team updates contact records with valid company references before the migration run to avoid quarantine blocks.

If your FastTrack data distinguishes between prospect and customer contacts via a status property, we split the migration: prospects without a closed-won deal route to Salesforce Lead; active customers route to Contact. We apply your specified status-to-object rules before loading.

FastTrack Company maps 1:1 to Salesforce Account. Parent-child company hierarchies in FastTrack map to Account.ParentId — the parent company must migrate first; we detect and flag circular references before loading. Accounts without a parent link create as top-level organizations in Salesforce's hierarchy.

FastTrack Deal maps to Salesforce Opportunity with the deal name as Opportunity.Name, deal amount as Amount, and close date as CloseDate. Stage mapping requires value-by-value mapping per Salesforce Sales Process; your Salesforce admin confirms stage pick-list values match FastTrack stage names before the migration run.

Each FastTrack pipeline becomes a Salesforce Sales Process keyed by a Record Type. Your Salesforce admin pre-creates record types before migration so stage pick-lists scope correctly per deal type. Multiple pipelines require multiple record types with distinct stage sets and page layout assignments.

Stage names map value-by-value against each Salesforce Record Type's stage pick-list. Stage probability and forecast category re-apply from Salesforce defaults; original stage-entry timestamps preserve as custom datetime fields. You must confirm stage value alignment during schema planning.

FastTrack call and email logs migrate as Salesforce Tasks with Type='Call' or Type='Email'. Meeting logs migrate as Salesforce Events with original start and end times. Original owner, create date, and parent record links (WhatId/WhoId) are preserved. Activities without a parent record link attach to the nearest contact by email domain match.

FastTrack notes migrate as Salesforce Notes (modern object, not legacy Note). Rich-text formatting is preserved. Notes without a parent record link are attached to the nearest contact or company by email domain match. Notes without any attachable parent are flagged for manual assignment before the migration completes.

FastTrack custom objects migrate 1:1 to Salesforce custom objects. Custom object title maps to the custom object's name field. Your Salesforce admin sets the sharing model and deployment status before data loads. All custom object fields require explicit field mapping in the migration specification.

FastTrack N:N relationships between custom objects map to Salesforce junction custom objects with two lookup fields. We generate the junction object schema and migrate link records during the data load phase. Junction objects require unique record naming conventions to prevent duplicate relationship entries.

FastTrack owner_id resolves by email match against Salesforce User records. Unmatched owners are flagged before migration — your team either invites them to Salesforce or assigns a fallback owner. No record lands without an OwnerId; all unmatched owners require resolution before the migration run.

FastTrack file attachments re-upload to Salesforce Files (ContentDocument/ContentVersion). Files over 25MB are chunked or flagged for manual upload post-migration. Inline images embedded in notes are downloaded and rehosted; image URLs update to Salesforce-hosted URLs in migrated note bodies.

Workflows, sequences, and automation rules do not migrate. We export FastTrack workflow definitions as structured JSON and PDF reference documents so your Salesforce admin can rebuild them in Flow. Export includes trigger conditions, action sequences, and field update specifications for complete rebuild documentation.