Migrate from OplaCRM to Microsoft Dynamics 365 Sales

OplaCRM Accounts map directly to Microsoft Dynamics 365 Sales Account. We use the account name as the primary dedupe key and external_id where present. Address data maps to the Account's compound address fields (address1_line1, address1_city, address1_statecode, address1_postalcode, address1_country). The OplaCRM healthscore numeric value maps to a custom field on Account — healthscore__c — as a preserved read-only signal; the scoring algorithm itself is opaque and cannot be replicated in Dynamics 365, so we flag this in the handoff for manual review or Power Automate-based rollup rebuilding.

OplaCRM Contacts map to Microsoft Dynamics 365 Sales Contact. Email is the deduplication key. The contact-to-account link resolves via Account external_id matching to populate the parentcustomerid field on Contact. Role, phone, and custom field values migrate directly. Any OplaCRM Contact without a matching Account creates a placeholder Account in Dynamics 365 to satisfy the Lookup relationship.

OplaCRM Opportunities map to Microsoft Dynamics 365 Sales Opportunity. Stage maps by display label to a Microsoft Dynamics 365 Sales Process stage name — we resolve sale_process_stage string values against the target org's stage list rather than by internal enum to prevent CLOSE_WON landing in the wrong bucket. Close date, close reason, and win/loss status map to estimatedclosedate, closeprobability, and the stage name itself. Owner resolves by email match to the Dynamics 365 User table.

OplaCRM Products map to Microsoft Dynamics 365 Sales Product2 records with Standard Price Book entries created at migration time. Product name and SKU (hs_sku equivalent) migrate directly; pricing logic may need review if OplaCRM stores list price in a non-standard currency format. We create a Pricebook2 entry at Standard price during import so Line Items can reference it.

Microsoft Dynamics 365 Sales does not have a native Invoice object in the same sense as OplaCRM's CreateOpportunityInvoiceDto. We map invoice amount, date, and status to a custom Invoice entity created in Dataverse before migration, with a Lookup to the parent Opportunity. If the customer also uses Dynamics 365 Business Central, we document the ERP-level invoice mapping as a separate integration concern rather than a CRM migration task.

OplaCRM CustomFieldValueDto key-value pairs map to Dataverse custom fields on the respective entity. We create each custom field in the Dynamics 365 target environment before data import using the appropriate Dataverse field type (string, integer, decimal, boolean, picklist). Naming collisions are handled by prefixing with opla_ and surfacing in the pre-flight mapping table for the customer to rename or merge before cutover.

OplaCRM sale_process_stage string enums map to Microsoft Dynamics 365 Sales Process stage values by display label. We pre-configure the Sales Process in the Dynamics 365 target environment, setting StageProbability percentages to match OplaCRM stage weights where documented. Loss reasons and win reasons from OplaCRM become custom fields on Opportunity if the destination org does not have them natively.

OplaCRM opportunities_joint_id UUID values identifying joint or co-selling opportunities are resolved into explicit relationship records. We create a custom field joint_opportunity_id__c on Opportunity to store the linked opportunity reference, or use the Dynamics 365 Connections entity if the customer chooses a relationship-based model. The pre-flight design session determines the approach; we document the chosen model in the mapping table and flag any UUID that cannot resolve to a target Opportunity record.

OplaCRM's locked boolean flag preventing record edits maps to a custom field opla_locked__c on each entity. Microsoft Dynamics 365 Sales does not support native record-level locking, so we set this as a boolean custom field and flag it in the post-migration handoff for the customer's admin to enforce via field-level security or a Power Automate flow that prevents edits on flagged records.

OplaCRM tag arrays on records map to Microsoft Dynamics 365 Sales multi-select picklist fields on the respective entity. Any comma-delimited tag strings are split into individual entries during the transform phase. The customer chooses which entity carries the tag field during scoping; common placements are Account and Contact.

OplaCRM attachments referenced by URL or file ID are downloaded and re-uploaded. Small files (under 5 MB) migrate as Dataverse Note (Annotation) records attached to the parent entity via objectid and objecttypecode. Large binary attachments (over 5 MB) migrate to a configured SharePoint location with the URL stored in a custom field on the parent record. Extended migration windows may be required for large attachment volumes.

OplaCRM Users map to Microsoft Dynamics 365 Sales Users by email address. Owner assignments on Opportunities, Contacts, and Accounts resolve via this User mapping. Any OplaCRM User without a matching Dynamics 365 User record is placed in a reconciliation queue for the customer's admin to provision before record import proceeds past the User validation step.