Migrate from OnePageCRM to Microsoft Dynamics 365 Sales

OnePageCRM Contacts are the primary record and include both unqualified prospects and qualified buyers in one object. We split at migration time based on OnePageCRM status: contacts with status indicating unqualified prospect (e.g., New Lead, Contacted) map to Dynamics 365 Lead; contacts with status indicating qualified buyer (e.g., Customer, Active) map to Dynamics 365 Contact attached to a pre-created Account. The original OnePageCRM status value migrates as a custom field on both Lead and Contact for audit. Next Action date and Next Action text migrate as a Task record with ActivityDate set to the Next Action date and Subject containing the action text.

OnePageCRM Organizations map directly to Dynamics 365 Account. Organization name becomes Account Name; organization phone and address fields map to the corresponding Account fields. The Organization-to-Account linkage is established before Contact import so that AccountId is available as a lookup reference on Contact records. Custom fields on Organization migrate as custom fields on Account.

OnePageCRM Deals map to Dynamics 365 Opportunity. Deal name becomes Opportunity Name; amount, close date, pipeline, and stage migrate directly. Closed Won and Closed Lost status from OnePageCRM map to the corresponding Dynamics 365 stage names. OnePageCRM deal margin, commission, and cost fields migrate as custom Opportunity fields. Multi-month deal flags (if enabled) migrate as a custom field indicating deal duration pattern.

OnePageCRM contact statuses (e.g., New Lead, Qualified, Customer) become Dynamics 365 Lead Status values for the Lead split and Contact Status values for the Contact split. We capture the full status taxonomy during scoping and configure both picklists in the destination org before migration. Any statuses that do not map cleanly become a default Other/None value with the original status preserved in a text field.

OnePageCRM Lead Source values (e.g., website inquiry, phone call, referral) map to Dynamics 365 Lead Source picklist. Pre-populated OnePageCRM values migrate as picklist values in Dynamics 365; any custom lead source values created by the organization are added as new picklist entries before import.

OnePageCRM tags are a flat namespace assigned to contacts. We map them to a Dynamics 365 multi-select picklist field on Contact. If tag count exceeds the multi-select picklist limit (150 values), we map to Salesforce-style Topics using the Topic and TopicAssignment entities in Dataverse. The customer selects the strategy during scoping.

Admin-created custom fields on OnePageCRM Contacts must be pre-created in Dynamics 365 before migration. We provide a custom field checklist during scoping that specifies the OnePageCRM field name, type, and sample values for the customer to create as Lead and Contact custom fields in Dynamics 365. Field type mapping: OnePageCRM text becomes Dynamics 365 Single Line of Text; OnePageCRM number becomes Decimal or Whole Number; OnePageCRM date becomes Date; OnePageCRM dropdown becomes Picklist.

Organization-level custom fields from OnePageCRM map to Account custom fields in Dynamics 365. We verify schema parity during scoping and flag any fields that exceed Dynamics 365 character limits or use unsupported field types (e.g., multi-select on Organization where Account does not support it). Custom fields are deployed to the destination Sandbox before migration and validated before production cutover.

OnePageCRM notes and call logs attached to contacts are included in the contact export dataset. Notes migrate as Dynamics 365 Note records linked via Regarding (regardingobjectid) to the parent Lead, Contact, or Account. Call records migrate as Task records with TaskSubtype = Call, preserving call duration, disposition, and date. Note: email body content is not included in the OnePageCRM export; we document exactly which records have email content so the customer can decide whether to accept partial migration or pursue a third-party extraction tool.

OnePageCRM Predefined Actions are template task sequences assigned to contacts. We do not migrate Autoflow workflows as automation code, but we map saved action templates to Dynamics 365 Task Template entities. The action name, default due date offset, and sequence order migrate so that the customer's admin can recreate the template structure in Dynamics 365 Task Templates for recurring task generation. One email sequence per Autoflow limitation means multi-step nurture sequences require rebuild in Power Automate.