Migrate from Exsalerate to Freshsales

Exsalerate Accounts map directly to Freshsales Accounts. The Account Name, billing address, shipping address, phone, website, and owner assignment transfer field-to-field. We use the Account Name as the dedupe key during Freshsales import. Custom fields on Exsalerate Accounts migrate as Freshsales custom fields, which the customer provisions under Admin Settings before import. Accounts are imported first to satisfy the parent-record dependency for all child objects.

Exsalerate Contacts map to Freshsales Contacts, preserving the Account-Contact relationship by resolving the parent Account by name lookup. We run duplicate detection on email address before import to flag and merge records that may have been created independently in Exsalerate. Job title, phone numbers, email, and any custom contact fields transfer with field-type awareness for picklist, date, and numeric formats.

Exsalerate Opportunities map to Freshsales Deals. The Opportunity name becomes Deal name, Amount maps to Deal Amount, Close Date maps to Close Date, and Stage maps to the corresponding Freshsales pipeline stage. We pre-create the Freshsales pipeline with stage labels that match Exsalerate's stage names before migration, preserving the ordered sequence. Owner assignment resolves by email match against Freshsales Users.

Exsalerate Pipelines become Freshsales Pipelines. We configure the destination pipeline under Admin Settings with the same pipeline name and ordered stage sequence before Deals import begins. Each Exsalerate stage label becomes a Freshsales stage with matching name, and any colour metadata from Exsalerate stage tiles is stored in a custom field on the Deal for visual reference after migration.

Exsalerate Pipeline Stages map to Freshsales Deal Stages within the configured Pipeline. Stage probability percentages from Exsalerate transfer to the Freshsales stage probability field. Exsalerate's drag-and-drop stage ordering is preserved as the stage sequence index in Freshsales. Stage-level automation triggers in Exsalerate are not migrated; we document them for the customer to rebuild in Freshsales' workflow builder.

Exsalerate colour-coded activity tiles map to Freshsales Tasks. The tile colour value (red, amber, green, blue) is stored in a custom picklist field on the Task record because Freshsales does not have a native colour-encoding model for task urgency. Due date, status (overdue, upcoming, completed), and the associated Account or Contact reference transfer directly. Task assignment resolves by owner email match to the Freshsales User.

Exsalerate Email Activities (subject, body, timestamp, sender, recipients) migrate as Freshsales Tasks of type email, linked to the associated Account or Contact. We preserve the original email timestamp as Activity Date for timeline ordering. Attachments require a separate file migration step and are linked as file attachments to the parent record in Freshsales. Email threading relationships are not preserved as Freshsales does not support thread ID tracking natively.

Exsalerate allows WorkflowMax quotes to be imported as Opportunities, creating a cross-reference that is not a standard CRM field. This linkage is a custom attribute in Exsalerate. We detect it during scoping, extract the WorkflowMax quote ID and job reference, and store them in a custom text field (wfm_quote_ref__c) on the Freshsales Deal. The customer rebuilds the WorkflowMax connection manually in Freshsales using Freshworks' native integration or a middleware connector.

Exsalerate user accounts map to Freshsales Users by email address match. We extract every distinct owner referenced on Account, Contact, Opportunity, and Task records during scoping. Any Exsalerate user without a matching Freshsales User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Exsalerate users are assigned to a placeholder owner flagged for reassignment post-migration.

Custom fields on Exsalerate Accounts, Contacts, and Opportunities migrate to Freshsales custom fields of equivalent type. We map picklist values, date formats, and numeric precision during the field mapping phase. Any custom field that cannot be matched to an equivalent Freshsales field type is flagged in the scoping report with a recommended approach: either a text field fallback or a note in the migration record. Custom fields are provisioned in Freshsales before any data import begins.