Migrate from OPEX 365 CRM to Zoho CRM

OPEX 365 CRM Contacts are standard Dataverse entities that map directly to Zoho CRM Contacts. The Dataverse contactid serves as the source of truth for referential integrity during migration. We preserve full name components (firstname, lastname), email address (used as dedupe key), phone numbers, address fields, and lifecycle stage as a custom field in Zoho since Zoho CRM does not have a native lifecycle stage concept. Owner assignments map via Dataverse systemuser email to Zoho Users by email match. Any Contact with an inactive or missing source owner gets reassigned to the designated migration owner pending admin review.

Dataverse Account records map to Zoho CRM Accounts with a direct field correspondence for name, industry, annual revenue, website, and address fields. The Dataverse accountid is used to resolve parent-child hierarchy where Accounts have parent Account relationships. We preserve the industry classification as a Zoho picklist field, creating any picklist values that do not already exist in the target Zoho instance. Account is created before Contact migration so that the Account-Contact relationship is satisfied at the moment of Contact insert.

OPEX 365 CRM Opportunities map to Zoho CRM Deals. The opportunitystage field maps to Zoho Stage with the probability percentage preserved in a custom numeric field since Zoho calculates stage probability differently. Estimated close date migrates to Expected Close Date, and actualclose datetime maps to Closed Date. The Dataverse opportunityid is preserved for lookups from related records. Pipeline assignments from OPEX 365 CRM map to Zoho Pipeline, and we configure the Zoho pipeline structure before migration begins to ensure stage values are available at import time.

Dataverse Lead records map to Zoho CRM Leads with a direct field correspondence for name, company, email, phone, and lead status. The original Dataverse leadscore and leadqualitycode values migrate to custom numeric fields in Zoho since Zoho does not have a native lead scoring field. Lead source information from Dataverse maps to Zoho's Lead Source picklist, with new picklist values created as needed. We flag any Leads that have already been converted in OPEX 365 CRM so they are not re-imported as Leads but rather processed through the Contact path.

OPEX 365 CRM activities (activitypointer) are polymorphic with activityparty records that can reference Contacts, Accounts, Leads, or Users via partyid. Zoho CRM uses strict party-type fields requiring a pre-resolution pass. We enumerate every activityparty record, resolve each partyid to its target type and Zoho record ID, and create placeholder records for any missing targets before Activity import begins. Emails from Dataverse map to Zoho Tasks with Sub-Type set to Email; phone call records map to Zoho Calls; appointments map to Zoho Events. Activity timestamps are preserved via Activity Date and Created On fields.

OPEX 365 CRM Cases (Dataverse incident entity) map to Zoho CRM Cases with status, priority, subject, and entitlement associations preserved. Case origin maps to Case Source in Zoho, and the Dataverse incidentid is retained for related record lookups. Case title migrates to Case Subject, and case description maps to the Case Description field. We link Cases to their originating Contact and Account by resolving the customerid and accountid lookups at migration time.

Dataverse Product records (productid, name, productnumber, standardcost, price) map to Zoho CRM Products. Pricing information linked via the productpricelevel entity migrates as Zoho Price Books. Bundle and product bundle item relationships in Dataverse may require manual reassembly in Zoho's product bundling UI since Zoho handles bundles differently from Dataverse's productassociation entity. Product code from Dataverse maps to the Zoho Product Code field.

Custom Dataverse entities discovered via the EntityDefinitions endpoint map to Zoho CRM custom modules. We enumerate all custom entities and their attribute metadata before migration so that custom fields are pre-created in Zoho with correct data types rather than relying on Zoho's auto-import field creation which may assign incorrect types. Custom entity relationships (Dataverse lookups and many-to-many intersect entities) map to Zoho lookup fields and linking modules. Zoho auto-creates custom modules from CSV files with a _C suffix in the filename; our pipeline respects this convention when creating modules via the API.

Notes and email attachments in OPEX 365 CRM are stored as Dataverse annotation entities with base64-encoded file content. Standard API exports do not include attachment bodies by default. We extract annotation records separately using the Dataverse API and store binary content in our staging blob storage, then upload each file to Zoho's document attachment endpoint, linking it to the corresponding Contact, Account, Deal, or Case via the object ID and module lookup. This adds a distinct extraction and re-upload step to the migration sequence but is required to avoid losing file attachments. Note text content migrates as Zoho Notes linked to the parent record.

Dataverse SystemUser records map to Zoho CRM Users by email address match. The Dataverse systemuserid serves as the migration key for owner assignment on all record types. Any Dataverse owner without a matching Zoho User email address goes to a reconciliation queue for the customer's Zoho admin to provision before record import resumes. We do not migrate Dataverse security roles, business unit hierarchy, or Azure Active Directory configurations; these are recreated manually in Zoho based on the FlitStack AI migration inventory.