Migrate from X2CRM to Salesforce Sales Cloud

X2CRM Contacts with no associated Deal or with a status indicating pre-qualification map to Salesforce Lead. X2CRM Contacts linked to an Account with an active or won Deal map to Salesforce Contact attached to an Account. We compute the split during scoping using X2CRM's Contacts module fields (lifecycle stage tag, associated account link, deal association). The original X2CRM contact record ID is preserved in a custom field x2crm_contact_id__c on both Lead and Contact for audit and cross-reference.

X2CRM Accounts map directly to Salesforce Account. The X2CRM Account website field maps to Account Website, industry and type map to standard Account fields, and the annual revenue and employee count map to corresponding custom or standard fields. Account is created before any Contact import so that AccountId lookups are satisfied at the moment of Contact insert.

X2CRM Deals map to Salesforce Opportunity. The deal stage property maps to Salesforce StageName using a stage-mapping table defined during scoping. If X2CRM uses a custom stage label not present in Salesforce's standard stage set, we add it to the active Sales Process before migration. Closed-Lost reason and probability percentages migrate from X2CRM custom fields to Salesforce LossReason and DefaultProbability.

X2CRM's single deal pipeline maps to a Salesforce Record Type on Opportunity with a corresponding Sales Process. If the customer has configured multiple pipeline views in X2CRM using custom module workarounds, each unique pipeline intent becomes a separate Salesforce Record Type with its own stage values and Page Layout.

X2CRM Products map to Salesforce Product2 records. The product name, SKU (productCode), and description migrate directly. We create Standard Pricebook entries during migration so that migrated Deals can reference products without requiring a separate pricebook setup step. Product2 is created before any Deal with line items migrates.

X2CRM Services (recurring service contracts or subscriptions linked to Accounts) map to Salesforce Asset if the destination org has Service Cloud and the customer tracks contractual assets. If the customer uses Cases for service tracking, Services map to Case with the associated Account linked via AccountId. The mapping decision is made during scoping based on the customer's post-migration service model.

X2CRM Marketing Campaigns map to Salesforce Campaign. Campaign name, type, status, and start/end dates migrate directly. Linked Contact associations migrate as CampaignMember records with Status derived from the X2CRM contact-campaign association status. Email campaign templates migrate as static HTML content stored in a custom field or attached Document for the customer's email team to reassign to Salesforce Email Template or Marketing Cloud.

X2CRM Activities split by type: call activities migrate to Salesforce Task with TaskSubtype=Call and CallDurationInSeconds preserved in a custom field; meeting activities migrate to Salesforce Event with StartDateTime, EndDateTime, and Location preserved; standalone task activities migrate to Salesforce Task with Status, Priority, and ActivityDate preserved. All Activity records resolve their related Contact or Deal lookup at migration time using the X2CRM association record to set WhatId and WhoId on the Salesforce record.

X2CRM Action records of type Note or Comment migrate to Salesforce Note linked via ContentDocumentLink to the parent Contact, Account, or Opportunity. Note body migrates as plain text; any embedded file references are resolved by the attachment migration process. Note ordering is preserved by setting CreatedDate to the original X2CRM timestamp.

X2CRM Tags are standalone label records applied across multiple module types. We inspect all unique tag values during discovery, create a custom multi-select picklist field on the relevant Salesforce objects (typically Contact and Account), and reapply tag associations during the post-import reconciliation phase. If tag count exceeds the 500-value limit for multi-select picklist, we use a custom tag junction object instead.

X2CRM User records map to Salesforce User by email match. We extract every user referenced as an owner on Contacts, Accounts, Deals, and Activities and match against the destination Salesforce org's User table. Any X2CRM user without a matching Salesforce User is flagged in the reconciliation queue for the customer's admin to provision before record migration resumes. Inactive X2CRM users map to inactive Salesforce Users so historical assignment is preserved.

X2CRM custom fields added via the module builder vary by module and require field-level mapping during scoping. We inspect the X2CRM field schema via API discovery (field name, data type, required flag) and align each custom field to a typed Salesforce custom field (__c API name). Lookup relationships between custom modules resolve through parent-record lookup resolution. Custom module schema must be pre-created in Salesforce before data migration begins.

X2CRM attachment records linked to Contacts, Accounts, Deals, and other modules migrate as Salesforce ContentDocument records attached via ContentDocumentLink. We download files from X2CRM's attachment storage (REST API for SaaS; local disk path for self-hosted) and upload to Salesforce via the Connect API. For self-hosted X2CRM, we coordinate with the customer's IT team during discovery to expose the upload directory via admin panel or SSH access before attachment migration begins.