Migrate your OPEX 365 CRM data

Contacts are standard Dataverse entities with a well-documented schema. We migrate all standard contact fields including name, email, phone, address, and lifecycle stage. Owner assignments map via the systemuser entity.

Accounts are the parent entity for Contacts in the Dataverse model. We preserve the parent-child hierarchy during migration and map industry classification, annual revenue, and address fields to their destination equivalents.

Opportunities map to Deals in most destination CRMs. Pipeline and stage names vary significantly between OPEX 365 CRM implementations, so we capture the source stage label and estimated close date and remap them during import.

Leads are a separate object in Sales Hub but may not exist in all destination CRMs. Where the target does not have a separate Lead object, we merge Lead records into Contacts and preserve lead_status as a custom contact property.

Emails, phone calls, tasks, and appointments are stored as activitypointer records with polymorphicParty relationships. We flatten these to standard activity objects in the destination, preserving the regarding_objectid link where the target schema supports it.

Cases (incidents) are fully documented Dataverse entities with status, priority, subject, and entitlement associations. We preserve case history and link cases to their originating Contact and Account.

Product records include pricing information linked via bundle and productpricelevel entities. We migrate the product catalog with pricing tiers, noting that bundle structures may need manual reassembly in the destination if it lacks a bundling concept.

Custom entities created in Dataverse are accessible via the Dataverse API. We enumerate custom entity schemas during discovery and generate field-level mappings for each, handling data type conversions where source and target field types differ.

Notes are stored as annotation entities with base64-encoded file content. We extract attachments and store them as discrete files, remapping them to the corresponding target records using the objectid reference.

User records in Dataverse include security roles and business unit assignments. We map source users to target users by email address and flag any unmapped owner references so orphaned record assignments can be resolved post-migration.

Pipeline and stage configurations are organizational metadata that do not migrate automatically. We document the source pipeline/stage structure and recreate it in the destination, then remap opportunity records to the new stage values.