Migrate from ForceManager CRM to Microsoft Dynamics 365 Sales

ForceManager Company records map to Microsoft Microsoft Dynamics 365 Sales Account. The company name, type, rating, and responsible user fields migrate directly. We use the company name as the Account dedupe key during import. Account must be created before any Contact import so that the parent AccountId lookup is satisfied at Contact insert time. Any z_ prefixed fields on Company are introspected via the Fields menu during scoping, then recreated as Dataverse custom fields before migration.

ForceManager Contact records map to Microsoft Dynamics 365 Sales Contact, preserving parent AccountId from the Account mapping. Standard fields (name, email, phone, job title) map directly. z_ prefixed extra fields on Contact are recreated as Dataverse custom fields using the label retrieved from the ForceManager Fields endpoint, replacing the system-prefixed key with a human-readable API name. Owner assignment resolves via email match against the Dynamics 365 User table.

ForceManager Opportunities map to Microsoft Dynamics 365 Sales Opportunity. Stage names from ForceManager map to the nearest Microsoft Dynamics 365 Sales Process stage, and we recommend creating a custom Sales Process matching the source pipeline before migration. Closed-Lost and Closed-Won reasons from ForceManager custom fields migrate to the Dynamics 365 Status Reason field. The estimated value and probability migrate to Amount and the stage probability configured in the Sales Process.

ForceManager Activities representing logged calls and meetings map to Microsoft Dynamics 365 Sales Task (TaskSubtype = Call) and Appointment respectively. GPS coordinates attached to ForceManager activity records migrate to a custom Dataverse field capturing the original location. We replay the full activity timeline in Dynamics 365 by setting the Activity Date to the original ForceManager timestamp so that sales managers see the historical sequence when opening an Account or Contact. Notes migrate as Dynamics 365 Note records linked via Regarding to the parent Account or Contact.

ForceManager Events (calendar entries with GPS location, attendee associations, and time) map to Microsoft Dynamics 365 Sales Appointment records. Start Time, End Time, Location (including GPS coordinates), and attendee list migrate directly. Attendees resolve to Contact or User records via email matching against the migrated Contact and User tables.

ForceManager Tasks (status, due date, assignee, description) map to Microsoft Dynamics 365 Sales Task. Task status (open, completed) migrates to the Dynamics 365 Task State field. Owner assignment resolves via email match against the Dynamics 365 User table. Completed Tasks retain their Activity Date from the ForceManager source for historical audit trails.

ForceManager Sales Orders and Sales Order Lines represent a transactional layer that Microsoft Dynamics 365 Sales handles differently. We map Order headers to Opportunity records with a custom Order_Number field and Order_Date captured as a custom field. Line items migrate as Opportunity Product entries linked to the Opportunity, resolving the Pricebook2 and Product2 references at migration time. If the destination org includes Dynamics 365 Business Central, we map Order data to Sales Order records in Business Central instead, which requires coordinating with the customer's ERP admin for account and product synchronization.

ForceManager User records are extracted via the /users endpoint and matched to Microsoft Dynamics 365 Sales Users by email address. Any ForceManager Owner without a matching Dynamics 365 User is placed in a reconciliation queue for the customer's admin to provision before record migration resumes. Active and inactive status is preserved as a custom field on the User record to flag decommissioned source users who should not own records in Dynamics 365.

All ForceManager custom fields carry a z_ prefix in API payloads (e.g., z_internal_currency, z_text_special) without embedded display labels. We query the ForceManager Fields endpoint during scoping to capture the label-to-prefix mapping, then create Dataverse custom fields with human-readable names before migration begins. Field types (text, number, date, picklist, currency) are inferred from the payload values and mapped to the equivalent Dataverse column type. This step must complete before any data import to avoid type mismatches on custom field inserts.

ForceManager Views (saved list filters exported via /views) represent configuration rather than data. We document the filter structure, sort order, and column selection for each View and provide a written guide for manual recreation in Microsoft Dynamics 365 Sales using Advanced Find and personal views. Views with complex filter logic that cannot be replicated via Advanced Find are flagged for Power Automate or a custom Power Apps solution.