Migrate from LeadMaster to Salesforce Sales Cloud

LeadMaster Accounts map directly to Salesforce Account. Primary address, billing address, phone, industry, employee count, and any custom account properties transfer as typed Salesforce fields. The account name serves as the dedupe key during import. We resolve any orphaned custom fields by falling back to a Salesforce custom text field on Account if no standard field equivalent exists.

LeadMaster Leads map directly to Salesforce Lead. The core fields (name, email, phone, company, status, source, rating) transfer to their Salesforce equivalents. LeadMaster's Smart Queue filters do not migrate as saved searches; we document each Smart Queue definition and map it to a Salesforce list view or segment for manual recreation. Owner assignment migrates via email lookup against the Salesforce User table.

LeadMaster Opportunities map to Salesforce Opportunity. Pipeline stage, amount, close date, probability, and owner transfer. Custom Opportunity properties (product lines, deal sources, competitive notes) map to custom Opportunity fields created during schema design. Stage probabilities are rounded to Salesforce-allowed integers and mapped against a Salesforce Sales Process configured before migration.

Each LeadMaster pipeline stage becomes a Salesforce StageName value within a Sales Process. We map stage order and probability percentages from LeadMaster to the Salesforce stage setup. Closed-Won and Closed-Loss reasons in LeadMaster migrate to Salesforce Loss Reason and custom win/loss fields on Opportunity.

LeadMaster Smart Queues (saved filters for inside-sales team management) are documented during discovery but do not replicate as executable filters in Salesforce. We deliver a Smart Queue mapping table showing which Salesforce standard list views each Smart Queue should produce, including filter criteria for rep-level and manager-level queue recreation.

LeadMaster's help desk module Cases map to Salesforce Case if the destination org includes Service Cloud or has the Case object enabled. Case number, status, priority, origin, description, and resolution migrate. Conversation threads migrate as EmailMessage records linked to the Case. If the destination Salesforce org does not have Service Cloud, Cases migrate as Tasks on the related Account or Contact.

LeadMaster User accounts and Owner assignments map to Salesforce User by email match. We extract every owner_id referenced on Lead, Account, Opportunity, and Case and resolve against the destination Salesforce org's User table. Any LeadMaster user without a matching Salesforce User enters a reconciliation queue for admin provisioning before record import begins.

LeadMaster logged email activity maps to Salesforce Task with an associated EmailMessage record. The Task provides the activity timeline entry (WhoId, WhatId, ActivityDate); the EmailMessage holds subject, body, from, to, and direction. We resolve parent WhoId references (Lead or Contact) and WhatId references (Opportunity or Account) before insert.

LeadMaster call logs map to Salesforce Task with TaskSubtype=Call. Call duration, disposition, and any notes transfer to custom Task fields. ActivityDate preserves the original timestamp to maintain timeline ordering. We resolve the parent WhoId and WhatId at migration time.

LeadMaster calendar events migrate to Salesforce Event. StartDateTime, EndDateTime, Subject, and Location transfer directly. Attendee mapping creates EventRelation records linking to the resolved Lead, Contact, or User.

LeadMaster notes migrate as Salesforce Note records linked via ContentDocumentLink to the parent Account, Lead, Opportunity, or Contact. Note body transfers as plain text or rich text depending on the source format. We preserve the original created date and author if available.

LeadMaster marketing campaigns migrate to Salesforce Campaign. Campaign name, type, status, start and end dates, budgeted cost, and expected revenue transfer. Campaign member associations (which Leads or Contacts were added to which campaigns) migrate as CampaignMember records. Email template content migrates as Salesforce EmailTemplate records where the destination org has the EmailTemplate object accessible.

LeadMaster custom form field definitions and submitted responses require a dual-step approach. Form field definitions are documented during discovery for admin replication in Salesforce. Submitted response data stored against Lead or Account records migrates to Salesforce custom fields (created pre-migration) or a structured long-text area field where no standard equivalent exists. We flag any form field with no Salesforce type match during scoping.

File attachments stored against Lead, Account, Opportunity, or Case records migrate as Salesforce ContentVersion records linked to the parent via ContentDocumentLink. We export from LeadMaster, stage in cloud storage, and upload to Salesforce using the Bulk API with chunking for large files. File size limits and Salesforce storage quotas are confirmed before migration begins.