Migrate from OPEX 365 CRM to Freshsales

OPEX 365 CRM Contact records map directly to Freshsales Contact. The Dataverse contactid is preserved in a custom field src_contactid__c for audit. Email, phone, address, lifecycle stage, and owner assignments transfer to Freshsales equivalent fields. Owner resolution uses email matching against Freshsales User records.

OPEX 365 CRM Account records map to Freshsales Account. The Account record is imported before any Contact import so that the parent Account lookup is satisfied at Contact insert time. Industry, annual revenue, website, and address fields transfer directly. Account is the parent entity for Contact in both systems.

OPEX 365 CRM Opportunity records map to Freshsales Deal. Pipeline stage names and probabilities vary across OPEX 365 CRM implementations, so we capture the source stage label, probability percentage, estimated close date, and amount during discovery and map them to Freshsales Deal stages. The customer configures the target pipeline structure in Freshsales before migration.

OPEX 365 CRM Lead records map to Freshsales Lead. Lead status, lead source, and any lead scoring fields transfer to Freshsales equivalent fields. Freshsales Lead conversion creates a corresponding Contact and Account. We preserve lead_status in a custom field src_lead_status__c for audit after conversion.

OPEX 365 CRM opportunity product records (linked via productpricelevel entities) map to Freshsales Deal Products. Product name, SKU, quantity, and unit price transfer. Bundle structures may require reassembly in Freshsales after migration.

OPEX 365 CRM activities use the activitypointer entity with polymorphic activityparty records whose partyid can reference Contacts, Accounts, Leads, or Users. We run a referential integrity pass that resolves each activityparty record to its correct target type and Freshsales record ID before importing. Unresolved party references create placeholder Contact records so activity assignments are not orphaned. Emails become Tasks with type email; calls become Tasks with subtype call; meetings become Events.

OPEX 365 CRM Notes are annotation entities with base64-encoded file content. We extract annotation records using the Dataverse RetrieveContent discharge API and store binary content in staging blob storage, then remap file references to Freshsales Attachments linked to the corresponding Contact, Account, Deal, or Lead record. Notes without attachments migrate as Freshsales Note records. This is a distinct extraction step because standard API exports do not include attachment bodies.

Custom Dataverse entities are enumerated via the EntityDefinitions API during pre-migration discovery. Each custom entity's attributes are mapped to Freshsales custom fields on the nearest standard object (Contact, Account, or Deal). On Growth plan, only custom fields on standard objects are available; Pro and Enterprise support additional custom object configuration. We deploy the custom field schema to the target Freshsales instance before data import begins.

OPEX 365 CRM Users map to Freshsales Users by email address. Owner references on Contact, Account, Deal, and Activity records are resolved to Freshsales User IDs at migration time. Any OPEX 365 CRM Owner without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes.