Migrate from erxes to Freshsales

erxes Contacts map to Freshsales Lead if the contact represents an unqualified prospect, or to Freshsales Contact if the contact is associated with a company and represents an active sales relationship. We determine the split by examining erxes custom fields for lifecycle status indicators, or by applying a default rule (all erxes Contacts migrate as Freshsales Contacts unless the customer specifies a Lead qualification criteria). The erxes primaryEmail becomes the Freshsales email field, used as the dedupe key. Custom field values on erxes Contacts map to Freshsales custom properties on the corresponding object.

erxes Company records map directly to Freshsales Account. The Company name becomes Account Name, and the primaryEmail or website maps to the corresponding Freshsales Account fields. erxes Companies linked to Contacts via companyId create the Account-Contact relationship in Freshsales during the Contact import phase. We resolve the Account record first so that the AccountId lookup is satisfied when Contacts are imported.

erxes Deals map to Freshsales Deals. The erxes deal amount, stage name, and pipeline assignment migrate to Freshsales Deal amount, deal stage, and pipeline. We map erxes Pipeline and Stage names to Freshsales pipeline and stage configurations that the customer pre-configures in Freshsales before migration. Closed-won and closed-lost statuses from erxes map to Freshsales deal statuses with probability percentages preserved.

erxes Pipelines define the sales workflow stages for Deals. We map erxes pipeline configurations including stage order, stage names, and probability mappings to Freshsales pipeline and stage configurations. The customer configures the Freshsales pipeline structure before migration, and we map the erxes stage IDs to the corresponding Freshsales stage IDs during import. Stage sequence and probability percentages transfer directly.

erxes Tasks migrate to Freshsales Tasks with title, description, due date, status, and owner assignment preserved. The erxes userId mapping resolves to Freshsales User records by email match. Tasks linked to specific Deals or Contacts carry the corresponding Freshsales lookup ID after parent record resolution. Task priority and status (open, completed) map directly to Freshsales Task fields.

erxes multi-channel Conversations (email, SMS, chat, WhatsApp) migrate to Freshsales as Notes attached to the corresponding Contact or Account record, or to a custom Conversation object if the customer configures one at Enterprise tier. The Conversation body, channel type, and customer association transfer, but channel-specific metadata (WhatsApp template IDs, SMS carrier information) does not have a Freshsales equivalent and is flagged in the migration report. Message threading order depends on erxes server timestamps, which we preserve as Note createdAt values.

erxes custom fields defined on Contacts, Companies, Deals, and Tasks migrate to Freshsales custom fields on the corresponding objects. We map the erxes field schema (field name, data type) to Freshsales field types: text fields to Text, date fields to Date, dropdowns to Picklist, multi-select to Multi-select Picklist. The customer pre-creates the destination custom fields in Freshsales before migration so that the field API names are available for mapping. erxes custom fields have no type enforcement on ingest, so we validate against erxes field definitions before mapping to prevent type mismatches in Freshsales.

erxes Users map to Freshsales User records by email match. Role and permission configurations in erxes (team-based access control) do not have a direct Freshsales equivalent because Freshsales uses a simpler role-permission model (Admin, Standard). We migrate User records with name, email, and active status, and the customer's Freshsales admin reviews role assignments post-migration. Any erxes User without a matching Freshsales User email goes to a reconciliation queue for manual provisioning.