Migrate your X2CRM data

Contacts is the core record type in X2CRM, storing name, email, phone, and address fields as standard properties. We map Contacts 1:1 via the REST API endpoints using application/json. Custom contact fields are preserved as-is and transferred as supplementary properties on the Contact record.

Accounts represent companies and organizations linked to Contacts. We migrate Accounts including associated tags, lifetime value, and linked Contact relationships. The API supports filtering by account type and we handle deduplication against imported Contacts.

Deals track sales opportunities with stage, value, probability, and expected close date. We map Deals and preserve Pipeline stage associations, deal owners, and activity history logs attached to the deal record.

X2Flow (X2WorkFlow) stores automation as trigger-action pairs with drag-and-drop configurations. Workflows do not export as portable data—they must be manually rebuilt at the destination or mapped conceptually to the new platform's automation engine. We document every X2Flow trigger type and action for reconstruction guidance.

Products catalog items with pricing, SKU, and description. We migrate Products and preserve associated price books. Line-item associations with Deals are preserved via deal mapping.

Services track recurring service contracts or subscriptions linked to Accounts. We transfer Services including status, renewal dates, and associated Account links.

Campaign records store campaign name, type, status, and associated mailing lists. Campaign history and linked contacts are preserved. Email campaign templates are migrated as static HTML where the destination supports rich-text import.

Activities include calls, meetings, and tasks with timestamps, owners, and related Contacts or Deals. We sequence Activities in chronological order and map related record IDs to their new destination values.

Tags are standalone label records that can be applied to multiple object types. We migrate all Tags and reapply them to their target records post-import, maintaining the many-to-many associations.

Custom fields added via the module builder vary by module and require field-level mapping during migration scoping. We inspect the X2CRM field schema via API discovery and align each custom field to its destination equivalent or store it as a note property if no match exists.

User accounts include name, email, role, and assignment permissions. Role configurations (viewer, editor, admin) must be mapped to the destination's permission model. We export user records but ownership reassignments require explicit customer direction.

Attachments are stored as file references or blobs linked to records. We attempt to download and re-upload files during migration. If the attachment storage backend is a local disk path (self-hosted X2CRM), we coordinate with the customer to expose the file store for extraction.