Migrate from Followup CRM to Microsoft Dynamics 365 Sales

Followup CRM contacts map 1:1 to Dynamics 365 contacts. The primary company link in Followup CRM (a required or optional field depending on setup) maps to Contact.ParentCustomerId — requires the corresponding account to exist in Dynamics first. Owner assignment resolves by email match to Dynamics system users.

Followup CRM companies map to Dynamics 365 accounts with direct field-name correspondence for name, website, phone, and address fields. Optional fields such as industry, number of employees, and revenue also map to their Dataverse counterparts when present. Parent‑company hierarchies in Followup CRM (if configured) map to Account.ParentAccountId — circular references flagged and resolved before migration commits.

Followup CRM deals map to Dynamics 365 opportunities. The deal name becomes Opportunity.Name, amount maps to Opportunity.Amount, and close date maps to Opportunity.CloseDate. Owner resolution happens by email match against Dynamics system users with a fallback to a designated admin owner for any unmatched records.

Followup CRM pipeline stages are pick-list values on the deal. Dynamics 365 Sales models stages as BPF stages tied to the opportunity form — each Followup CRM pipeline stage becomes a stage name in a BPF definition that we create during migration setup. Stage-enter timestamps from Followup CRM are preserved as custom datetime fields on the opportunity for reporting continuity.

Followup CRM tasks migrate as Dynamics 365 tasks with Subject, Description, ScheduledEnd (due date), and Priority preserved. The Regarding lookup attaches the task to the correct opportunity or contact in Dynamics. Original owner assignment resolves by email match. If the task includes a category, we add a custom option-set on the Task table and map values. Regarding lookup can target opportunity, contact, or account. Unresolved owners receive the fallback owner.

Followup CRM engagement records (logged emails, calls, meetings) map to their corresponding Dynamics 365 activity tables. Start time, end time, duration, and subject transfer directly. The Regarding field links each activity to the parent contact or opportunity record. If Followup CRM records an activity type, we map it to the Dynamics activity (Email, PhoneCall, or Appointment). Attachments migrate as notes on the activity record. Activity parties preserve N:N participant links.

Followup CRM custom fields (bid type, license numbers, trade specialties, project references) have no native Dynamics 365 equivalents. We create custom columns on the target Dataverse table using the Power Platform API — field type (text, number, option set) chosen based on Followup CRM's source data type.

Followup CRM goal tracking (bid volume targets, quota attainment) is a native feature with no direct Dynamics 365 counterpart at the CRM level. We migrate goal records as custom columns on the user or opportunity table and provide a Power BI template report to replicate the dashboard — this requires a Power BI Pro license on the Dynamics side.

Files attached to Followup CRM deals or contacts are downloaded and re-uploaded to the corresponding Dynamics 365 record's SharePoint document location (if SharePoint integration is configured) or as Dynamics Notes attachments. File size limits of 25 MB per file in Dynamics apply.

Followup CRM users resolve against Dynamics 365 system users by email address. Active Followup CRM users must have corresponding Dynamics 365 user accounts provisioned before migration — we flag any unmatched owners and assign their records to a designated fallback owner.

Followup CRM's Procore integration stores project IDs and links that have no native Dynamics 365 equivalent. We migrate the project link value as a custom text column on the opportunity — Procore re-integration requires a separate Power Automate flow setup using Procore's connector.