Migrate from Exsalerate to Salesforce Sales Cloud

Exsalerate Account records map directly to Salesforce Account. Account Name, Billing Address, Phone, Website, Industry, and custom fields migrate as field-to-field mappings. Exsalerate's account-centric model means Account is created before any Contact or Opportunity import so that the lookup relationship is satisfied at the moment of child record insert. We use Account Name as the dedupe key during import.

Exsalerate Contact records map to Salesforce Contact with AccountId resolved from the parent Account lookup. We preserve FirstName, LastName, Email, Phone, Title, and custom fields. Duplicate detection runs on Email as the primary key before insert. If a Contact in Exsalerate has no associated Account, we create a placeholder Account or flag for the customer's admin to resolve before migration.

Each Exsalerate Pipeline becomes a Salesforce Record Type on Opportunity plus a corresponding Sales Process. Pipeline name becomes the Record Type label, and the pipeline's stage sequence becomes the Sales Process stage order. We configure these in Salesforce metadata before data import so that Opportunities land in the correct pipeline context immediately on insert.

Exsalerate stage labels (for example, 'Qualified', 'Proposal Sent', 'Negotiation', 'Closed Won') migrate to Salesforce Opportunity Stage picklist values. Stage order and colour-coding metadata from Exsalerate are preserved in a custom field exsalerate_stage_colour__c on Opportunity. We add the stages to the relevant Sales Process whitelist during pre-migration configuration.

Exsalerate Opportunity records map to Salesforce Opportunity with AccountId, OwnerId, and RecordTypeId resolved at migration time. Opportunity Name, Amount, CloseDate, StageName, Description, and custom fields migrate directly. If the Opportunity originated as a WorkflowMax quote import, we detect the WorkflowMax cross-reference field and populate the custom exsalerate_workflowmax_ref__c field on the Salesforce Opportunity.

Exsalerate to-do items map to Salesforce Task. Due date, status (Open, Completed), subject, and body migrate as standard fields. The Exsalerate tile colour value (used for urgency and context encoding) migrates to a custom picklist field exsalerate_tile_colour__c on Task. We verify that the destination Salesforce org has custom field access on Task during scoping since not all editions expose Task custom fields at no extra cost.

Exsalerate email history associated to Accounts and Contacts migrates to Salesforce EmailMessage records (the email content and headers) linked to an Activity Task record (the timeline entry). Subject, Body, FromAddress, ToAddress, and MessageDate transfer directly. The WhoId on Task points to the related Contact or Lead; WhatId points to the related Account or Opportunity. Attachments migrate as ContentDocument records linked via ContentDocumentLink.

Exsalerate user accounts map to Salesforce User records by email address match. We build a user mapping table during scoping. Inactive Exsalerate users are flagged in the mapping table and assigned to a placeholder Salesforce User (the customer's admin or a system integration user) during migration. Any Exsalerate user without an email match in Salesforce goes to a reconciliation queue for admin provisioning before production migration.

Custom fields on Exsalerate Accounts, Contacts, and Opportunities migrate to Salesforce custom fields with type-aware mapping: picklist values become Salesforce picklists, dates normalise to YYYY-MM-DD, numeric precision is preserved. We pre-create the Salesforce custom field schema (with __c API names) before any data import. Any Exsalerate custom field that has no Salesforce equivalent (rare, given Salesforce's flexible schema) is documented and either dropped or mapped to a text area field with an annotation in the migration log.

Exsalerate supports importing WorkflowMax quotes as Opportunities, creating a cross-reference that is stored as a custom attribute on the Opportunity rather than a standard lookup field. We detect this attribute during extraction by inspecting all Opportunity records for WorkflowMax identifiers. The reference value migrates to a custom text field exsalerate_workflowmax_ref__c on the Salesforce Opportunity, and we flag the field in the handoff document so the customer's admin can re-establish the WorkflowMax connection manually in Salesforce if needed.

Exsalerate's Xero integration stores contact and account cross-references that may exist as custom fields or notes within Exsalerate. We extract any Xero identifiers found in custom fields or note bodies and store them in a custom field exsalerate_xero_ref__c on the relevant Salesforce record. The customer's admin rebuilds the Xero-Salesforce connection using the Salesforce Xero AppExchange connector post-migration.

Exsalerate email activities, meetings (if captured), and to-do completions are loaded into Salesforce as Task, Event, and EmailMessage records in dependency order: Accounts first, then Contacts, then Activities linked to the resolved parent records. Activity timestamps are preserved by setting ActivityDate on Task and StartDateTime/EndDateTime on Event to the original Exsalerate values. Large activity histories (over 50,000 records) use Salesforce Bulk API 2.0 with chunking and exponential backoff on rate limit responses.