Migrate from X2CRM to Freshsales

X2CRM Contacts map directly to Freshsales Contact records via the X2CRM REST API contacts endpoint using application/json payloads. We preserve name fields (firstName, lastName), email, phone, address, and any custom contact fields discovered during schema scoping. Email serves as the dedupe key during Freshsales import. Historical tags applied to X2CRM Contacts migrate as Freshsales contact tags via the tag reapplication phase after initial import.

X2CRM Accounts (companies and organizations) map to Freshsales Account. We preserve company name, website, industry, annual revenue, employee count, and linked contact relationships. Account-Contact linkage is maintained by resolving the X2CRM accountId foreign key to the corresponding Freshsales Account record ID at import time. X2CRM's lifetime value field on Account maps to a Freshsales custom numeric field created during schema setup.

X2CRM Deals map to Freshsales Deal records. We preserve deal name, amount, stage, probability, expected close date, owner, and linked Account. X2CRM pipeline stage names are mapped to Freshsales Deal stages during configuration, and deal probability percentages transfer directly. Activity history logs attached to X2CRM Deals migrate as Freshsales Deal activities (calls, emails, meetings, tasks) linked via the deal relationship ID.

X2CRM Products catalog items map to Freshsales Product records, preserving SKU (mapped from X2CRM productCode), name, unit price, and description. Products are imported before Deals so that Deal-Product line-item associations can be resolved during Deal import. X2CRM price book associations transfer as Freshsales Product pricing records.

X2CRM Services track recurring service contracts or subscriptions linked to Accounts. Since Freshsales does not have a native Services module, we map Services to Deals with a custom Service Contract record type. Renewal dates, contract status, and associated Account links are preserved in custom Deal fields created during schema setup.

X2CRM Marketing Campaigns (name, type, status, mailing lists) have no direct Freshsales equivalent. We migrate campaign names as Freshsales contact tags prefixed with Campaign: and document the campaign list membership for the customer to rebuild using Freshsales Lists or Freshmarketer. Email campaign templates migrate as static HTML documents delivered in the handoff package.

X2CRM Activity records (calls, meetings, tasks with timestamps, owners, and related Contacts or Deals) map to Freshsales Activity records. We sequence Activities in chronological order and resolve related record IDs to their new Freshsales Contact and Deal IDs. Call duration and disposition from X2CRM migrate as Freshsales activity custom fields. Meeting location and attendee information preserves.

Tags are standalone label records in X2CRM that apply across multiple object types. We migrate all Tags as Freshsales Tag records and then reapply them to target Contacts, Accounts, and Deals post-import using the Freshsales API. The many-to-many tag associations are preserved in a tag-mapping table during migration scoping.

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 and align each custom field to an equivalent Freshsales custom field, creating the destination field in Freshsales before import begins. Field types (text, number, date, dropdown, checkbox) are mapped to Freshsales field types at configuration time.

X2CRM attachments are stored as file references or blobs linked to records. We download files via X2CRM API or file store access and re-upload to Freshsales via the Freshsales file attachment API, linking each file to the target Contact, Account, or Deal record. For self-hosted X2CRM instances, we coordinate SSH or admin panel access with the customer's IT team to expose the upload directory for file extraction.