Migrate from eSalesTrack to Salesforce Sales Cloud

eSalesTrack Lead records map directly to Salesforce Lead. The eSalesTrack lead status property maps to Salesforce LeadStatus. Any lead score or qualification data from eSalesTrack custom fields migrates to a custom field esalestrack_lead_score__c on Salesforce Lead. Owner assignment resolves by matching the eSalesTrack owner email against the Salesforce User table.

eSalesTrack Contact records map to Salesforce Contact. Each Contact requires an AccountId lookup, which is resolved during the extract phase by matching the Contact's parent Account name against the eSalesTrack Account data. If the Account does not exist in Salesforce yet, the Contact import waits for the Accounts phase to complete. Phone, email, title, and address fields map directly by name.

eSalesTrack Account records map directly to Salesforce Account. The AccountName field maps to Name, and the eSalesTrack website field maps to Website. Account is created first in the migration sequence so that Contacts can resolve their AccountId lookups. Any billing or shipping address data migrates to the corresponding Account address fields.

eSalesTrack Opportunity records map to Salesforce Opportunity. The eSalesTrack pipeline stage maps to Salesforce StageName, and the eSalesTrack pipeline name maps to a Salesforce Record Type on Opportunity. If eSalesTrack uses multiple pipelines, we configure a corresponding Record Type and Sales Process in Salesforce before migration begins. Closed-Lost and Closed-Won dates migrate to CloseDate and IsClosed flags.

Each eSalesTrack pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate from eSalesTrack to Salesforce StageProbability. Page Layouts are assigned per Record Type so that the pipeline-specific fields surface for the relevant sales team.

eSalesTrack Owner references on Lead, Contact, Account, and Opportunity resolve by email match against the Salesforce destination org's User table. Any eSalesTrack Owner without a matching Salesforce User enters a reconciliation queue. The customer's admin provisions missing Users before the corresponding records load. This is a blocking dependency: Opportunity and Contact imports cannot complete without resolved OwnerId values.

eSalesTrack task records (including calls and standard tasks) map to Salesforce Task. Task.Status, Priority, and ActivityDate preserve directly. Call tasks use TaskSubtype=Call with CallDurationInSeconds in a custom field if that data is present in the eSalesTrack export. Activity timeline ordering is preserved by setting ActivityDate to the original eSalesTrack timestamp.

eSalesTrack meeting records map to Salesforce Event. StartDateTime, EndDateTime, and Location preserve directly. If attendee data is present in the eSalesTrack export, we create EventRelation records linking the Event to the corresponding Salesforce Contact or Lead by matching the attendee email.

eSalesTrack notes migrate to Salesforce Note records. If eSalesTrack stores notes as rich text with attachments, the body migrates as rich text and the attachments migrate as ContentDocument records linked via ContentDocumentLink to the parent record (Lead, Contact, Account, or Opportunity). Note ordering preserves the original eSalesTrack timestamp as SystemModstamp.

eSalesTrack email engagements migrate to Salesforce EmailMessage records (the email content) linked to a Task record (the activity timeline entry). The WhoId on the Task points to the Lead or Contact; the WhatId points to the related Opportunity or Account. Email body and subject migrate directly; attachments migrate as ContentDocument records linked to the EmailMessage.

Any eSalesTrack custom fields on Contact not present in the standard field set are created in Salesforce before Contact migration begins. Field types are mapped: text fields become Text, date fields become Date, numeric fields become Number, and picklist fields become Picklist. Custom field API names follow Salesforce __c convention prefixed with es_ to avoid collision.

eSalesTrack custom fields on Opportunity are created in Salesforce as custom Opportunity fields before the Opportunity migration phase. Pipeline-specific custom fields are assigned to the corresponding Record Type's Page Layout. Validation rules on custom fields are documented separately and either disabled during load or set to skip validation for the migration user context.