Migrate from X2CRM to Microsoft Dynamics 365 Sales

X2CRM Contacts map to Dynamics 365 Leads or Contacts based on qualification status. We inspect the X2CRM contact record for tag associations (lead qualification tags, lifecycle tags) and field values to determine which records qualify as Contacts attached to Accounts versus Leads awaiting conversion. Unqualified or unsourced contacts become Dynamics 365 Leads; active customer contacts become Contacts linked to an Account. We preserve the original X2CRM contact ID in a custom field x2crm_contact_id__c on both Lead and Contact for audit and cross-reference.

X2CRM Accounts map directly to Microsoft Dynamics 365 Sales Accounts. Account name, website, industry, phone, address fields, and lifetime value migrate as typed Account fields. Account is created before Contact import so that the AccountId lookup is satisfied at the moment of Contact insert. Deduplication uses Account Name and Website as the matching key.

X2CRM Deals map to Dynamics 365 Opportunities. The deal stage maps to a Microsoft Dynamics 365 Sales Process and Opportunity StageName. Deal value, probability, expected close date, and owner migrate directly. Closed-Won and Closed-Lost reason fields from X2CRM custom fields become Dynamics 365 custom fields or map to the standard status change notes. Pipeline is resolved via Record Type mapping before migration.

X2CRM Products (catalog items with SKU, pricing, description) map to Dynamics 365 Product2 records. Standard Price Book entries are created during migration. ProductCode maps from the X2CRM product SKU field. Products must be imported before any Deals that reference them so that the PriceLevel and ProductId lookups resolve during OpportunityLineItem creation.

X2CRM Services track recurring service contracts or subscriptions linked to Accounts. Microsoft Dynamics 365 Sales does not have a native Services module; we map Services to either a Contract object (if Service Cloud is licensed) or to a custom Service_Contract__c object created during schema design. Renewal date, status, and linked AccountId are preserved in the migration.

X2CRM Activities (calls, meetings, tasks with timestamps, owners, and related Contacts or Deals) map to Dynamics 365 Task and Event records. Call disposition and duration map to Task custom fields or Event fields. Each Activity is linked to the resolved Contact or Account via the RegardingObjectId (Dynamics 365's WhatId equivalent). We sequence Activities in chronological order using the original X2CRM timestamp as ActivityDate for accurate timeline ordering in Dynamics 365.

X2CRM Marketing Campaigns (campaign name, type, status, associated mailing lists) map to Dynamics 365 Campaign records. Campaign history and linked contacts are preserved by creating CampaignMember records during migration. Email campaign templates are migrated as static HTML content if the destination Dynamics 365 org has marketing capabilities; otherwise they are flagged as content for rebuild in Dynamics 365 Customer Insights - Journeys or a marketing automation tool.

X2CRM Tags are standalone label records applied across multiple object types. We migrate all tag names to a tag library and reapply them to their target records. Tags on Contacts map to a custom multivalue field (tag__c as a multi-select picklist) or to Dynamics 365 Topics if the customer prefers topic-based classification. The customer selects the tag strategy during scoping.

X2CRM custom fields added via module builder vary by module and require field-level mapping during scoping. We inspect the X2CRM field schema via API discovery and align each custom field to a typed Dynamics 365 field (text, number, picklist, date, currency, lookup) before migration. Custom fields are pre-created in the Dynamics 365 org via the metadata API or manually before any data writes begin. API names follow the __c suffix convention.

X2CRM Users (name, email, role, assignment permissions) map to Dynamics 365 User records. We match by email address. Role configurations (viewer, editor, admin in X2CRM) are documented in the migration scope and mapped to Dynamics 365 security roles during the handoff. Owner assignment on Deals, Accounts, and Activities resolves via the User lookup. Users not yet provisioned in Dynamics 365 are held in a reconciliation queue for the customer's admin before record import resumes.

X2CRM file attachments are stored as file references or blobs linked to records. We attempt to download and re-upload files during migration. If the X2CRM instance is self-hosted with local disk attachment storage, we coordinate with the customer's IT team to expose the upload directory via SSH or admin panel access before migration scoping begins. Attachments are re-linked to their parent records (Contact, Account, Opportunity) in Dynamics 365 as Notes with file attachments or as ActivityMimeAttachment records on the activity timeline.