Migrate from FastTrack to Microsoft Dynamics 365 Sales

FastTrack Contact maps directly to Dynamics 365 Contact using one-to-one field mapping. The contact name, email address, phone numbers, job title, and address fields transfer as-is. Because Dynamics 365 requires each Contact to have an AccountId, any FastTrack Contact without a primary company is linked to a designated default Account record to preserve foreign-key integrity in Dataverse.

FastTrack Company maps 1:1 to Dynamics 365 Account. FastTrack's parent-company hierarchy maps to the Parent Account field on the Account record. Multi-company contacts that FastTrack holds as N:N associations collapse to one primary AccountId on the Contact; additional company associations are surfaced as Account Contact Relationships in Dynamics 365.

FastTrack Deal maps to Dynamics 365 Opportunity. The deal name, amount, close date, and description transfer directly. Pipeline stage values require a Business Process Flow (BPF) to be active on the Opportunity — the migration plan creates the BPF structure before the Opportunity data loads.

FastTrack's pipeline configuration (stages, stage order, probabilities) becomes a Dynamics 365 Business Process Flow. Each FastTrack pipeline generates one BPF; stage names and order are reproduced as BPF stages. Probability and forecast-category settings are re-applied as custom fields on the Opportunity.

FastTrack Lead maps to Dynamics 365 Lead using direct field mapping. Lead status values from FastTrack map to the Lead Status pick-list via a value-mapping table. FastTrack lead scores transfer as a new_customfield on the Lead entity, preserving the qualification context the score represented in FastTrack.

FastTrack email engagement records map to Dynamics 365 Email (Email) activity entities. The subject line, body text, sender address, recipient address, and sent timestamp are all preserved during migration. The Regarding lookup links each email to its parent Contact, Account, or Opportunity record, maintaining the contextual relationship in Dynamics 365.

FastTrack call records map to Dynamics 365 Phone Call activities. Call direction (inbound or outbound), subject line, duration in minutes, and the call timestamp transfer directly. The Regarding field on the Phone Call links to the associated Contact or Opportunity, preserving the relationship context from FastTrack.

FastTrack meeting records migrate as Dynamics 365 Appointment activities. Start time, end time, location, subject line, and attendee data are all preserved. The Regarding field on each Appointment links to the relevant Contact, Account, or Opportunity record, maintaining the calendar context in Dynamics 365.

FastTrack notes migrate to Dynamics 365 Annotations. Rich-text formatting stored in FastTrack notes is preserved as HTML in the Annotation Body field. Each note is linked via the Regarding field to its parent Contact, Account, Deal, or custom object record, ensuring notes remain associated with their original context in Dynamics 365.

FastTrack custom objects map 1:1 to Dataverse custom tables. The migration plan verifies the Dynamics 365 edition's table limit before committing — Sales Professional caps custom tables at 15, which may require collapsing FastTrack custom objects or upgrading to Enterprise before migration runs.

FastTrack file attachments are downloaded and re-uploaded to Dynamics 365's configured file storage (SharePoint Online or Dataverse file fields). File size limits and inline image handling follow Dynamics 365 storage rules. SharePoint must be provisioned and configured before the attachment migration phase runs.

FastTrack owner IDs are resolved by email match against Dynamics 365 SystemUser records. Unmatched owners are flagged before migration — the team either invites them to the Dynamics 365 tenant or assigns their records to a designated fallback user. A Source_System_ID__c custom field preserves the original FastTrack owner ID for audit continuity.