Migrate from Market Leader to Salesforce Sales Cloud

Market Leader contacts map directly to Salesforce Contacts. The critical dependency is that Salesforce requires an AccountId — contacts without a primary company in Market Leader get attached to a default 'Unassigned Accounts' record or a placeholder Account created during migration setup.

Market Leader contacts with lead_type='prospect' or lead_priority='high' and no closed deal route to Salesforce Lead. Contacts with a closed transaction or ongoing pipeline status route to Salesforce Contact under an Account. The split is determined by the presence of a deal_id and deal_stage in Market Leader.

Market Leader companies map to Salesforce Accounts. Company hierarchies (parent office / franchise relationship) preserved using Salesforce ParentId. Multi-contact accounts (Market Leader allows N:N contact-to-company) collapse to one primary AccountId per contact, with additional relationships surfaced as Account Contact Relations.

Market Leader deals map to Salesforce Opportunities. The deal pipeline and stage_name fields in Market Leader translate to Opportunity.StageName with value-by-value mapping to Salesforce stage pick-list values. Each unique Market Leader pipeline requires a Salesforce Sales Process and Record Type so stage values are scoped correctly.

Each Market Leader pipeline becomes a Salesforce Sales Process keyed by RecordTypeId. This is the primary schema-churn point: teams with multiple pipelines in Market Leader end up with multiple Salesforce Record Types, each needing its own page layout, profile assignment, and validation rules before data can map cleanly.

Market Leader stage_name values map to Salesforce Opportunity StageName pick-list values on a per-RecordType basis. Stage probability and forecast category are reapplied based on Salesforce's stage model. Stage-entered timestamps from Market Leader are preserved as custom datetime fields (Stage_Entered_Date__c) for reporting continuity.

Market Leader's agent_id on every contact and lead resolves by email match against Salesforce User records. Unmatched agent IDs are flagged before migration — your team either provisions Salesforce users first or assigns those records to a fallback user. No record lands in Salesforce without an OwnerId.

Market Leader call logs and email engagement records migrate as Salesforce Tasks (Type='Call' or Type='Email'). Original timestamps, owners, and parent-record links (contact_id or lead_id) are preserved. Drip sequence enrollment history is not a standard Salesforce object — it migrates as a custom field or audit note.

Market Leader custom properties — including mls_id, property_type, listing_status, and network_boost flags — require custom field creation in Salesforce before migration. We deliver a custom field creation plan (field label, API name, data type, pick-list values) so your Salesforce admin can pre-provision the schema before data lands.

Files attached to Market Leader contacts and deals re-upload to Salesforce Files. File size limits apply (default 25MB per file in Salesforce). Inline images in notes are downloaded and rehosted as Salesforce Files attached to the parent record. We also map the original file creation date to a custom field to preserve audit history.

Market Leader territory and network_boost flags control lead routing. Salesforce has a Territories feature (Enterprise edition and above) for territory management. We map these flags to custom fields (Territory__c, Network_Boost__c) or Salesforce Territory records depending on your edition. If you use Salesforce Territory Management, we create Territory records and link them to the appropriate users and accounts during migration.

Market Leader lead_source and campaign tracking migrate as custom fields (Original_Lead_Source__c, Original_Campaign__c). Salesforce Campaigns are a separate object — if you need full campaign history, we surface it in the migration plan for your admin to create Campaign records and link historical members.