Migrate from FIVE CRM to Microsoft Dynamics 365 Sales

FIVE CRM Contacts map directly to Microsoft Microsoft Dynamics 365 Sales Contact records. Standard fields (FirstName, LastName, Email, Phone, MobilePhone, Title, Address) transfer cleanly. Owner assignment (OwnerId) resolves by email match against the destination Dynamics 365 User table. We import Contacts after Accounts to satisfy the AccountId lookup required for Contact-to-Account linkage in Dynamics 365. Any FIVE CRM Contacts without a matching Account are held in a pre-import queue pending Account creation.

FIVE CRM Company records map to Microsoft Microsoft Dynamics 365 Sales Account. The Company Name becomes Account.Name, and the Company domain or website becomes Account.Website. Account is created before Contact import so that the AccountId lookup is satisfied at the moment of Contact insert. We use Company Name as the dedupe key to prevent duplicate Account creation during import.

FIVE CRM Lead records map to Microsoft Microsoft Dynamics 365 Sales Lead. The Lead Status, Lead Source, and any scoring properties from FIVE CRM transfer to corresponding Dynamics 365 fields (leadqualstatus, leadsourcecode, and custom score fields). FIVE CRM Lead-to-Contact conversion status is preserved as a custom field for reconciliation. We do not auto-convert Leads to Contacts during migration; the customer's admin performs that step post-migration.

FIVE CRM Deals map to Microsoft Microsoft Dynamics 365 Sales Opportunity. The FIVE CRM deal stage name maps to a Dynamics 365 Opportunity Stage, and the FIVE CRM pipeline assignment maps to a Microsoft Dynamics 365 Sales Process and Record Type that we configure before migration. Closed-Lost and Closed-Won dates and amounts transfer directly. The Deal amount becomes EstimatedRevenue on Opportunity. We resolve AccountId and OwnerId before inserting Opportunities to satisfy Dynamics 365's required lookup constraints.

FIVE CRM Pipelines (custom stage sets per tenant) map to Dynamics 365 Record Types on Opportunity, each paired with a Sales Process that whitelists the relevant stage values. We configure the Sales Process stages to match the FIVE CRM pipeline stage names and probabilities during pre-migration setup, deployed to Sandbox for validation before production migration. Probability percentages round to Dynamics 365-allowed integer values.

FIVE CRM Campaign records map to Microsoft Microsoft Dynamics 365 Sales Campaign. Campaign Name, Type, Status, and BudgetedCost transfer. Campaign membership (which Contacts and Leads are members of a given Campaign) migrates to CampaignMembers in Dynamics 365. FIVE CRM email engagement event logs (opens, clicks, replies) are not bulk-exportable; we migrate the campaign membership flag and the last engagement date but not the granular per-event timeline, which requires a separate export and manual import into Dynamics 365.

FIVE CRM Task records map to Microsoft Microsoft Dynamics 365 Sales Task. Subject, Description, DueDate, Priority, and Status transfer directly. Task assignment resolves OwnerId by email match against the destination User table. Completed tasks preserve the completion timestamp in the ActivityDate field. FIVE CRM task types (call, email, meeting, generic) map to Task.Subject prefixes and custom Task Type fields for differentiation at the destination.

FIVE CRM custom fields are heavily used to support telemarketing-specific data capture and do not have a public schema document exposed via API. We conduct a pre-migration field mapping session to enumerate every custom field in use, confirm its data type against the FIVE CRM export, and agree on a Dynamics 365 field mapping before migration begins. We pre-create custom fields in Dynamics 365 with correct field types (text, number, picklist, date, lookup) deployed to Sandbox for validation. Skipping this step leads to silent type coercion or dropped values because Dynamics 365 enforces field types at insert time.