Migrate from Leadforce CRM to Salesforce Sales Cloud

Leadforce Leads map to Salesforce Lead records. Standard fields (name, email, phone, source, status) migrate directly. Company name from Leadforce's embedded company data becomes the Company field on Salesforce Lead. Custom lead fields are mapped to Salesforce custom fields (custom__c) after the discovery screen-share phase enumerates the field list. Leadforce Lead status values map to Salesforce Lead Status with a custom field preserving the original Leadforce status for audit.

Leadforce often does not use a separate Companies object; company information lives within Lead records. We extract distinct company names and domains from Leadforce Leads, deduplicate them, and create Salesforce Account records first. Each Lead's company field then links via AccountId lookup during Contact creation. If the customer uses a separate Companies section in Leadforce, we treat it as a distinct Account import with the same deduplication logic.

If Leadforce exposes a separate Contacts object (not all instances do), we map it to Salesforce Contact with AccountId resolved via the Account deduplication pass. Contact name, email, phone, title, and custom fields migrate directly. Where Leadforce stores contact data only inside Leads, we split at the Account creation step and generate Contact records from the Lead email and name data with AccountId lookup satisfied.

Leadforce Deals map to Salesforce Opportunity. The deal name becomes Opportunity Name, monetary value migrates to Amount, close date migrates to CloseDate, and stage name maps to StageName. If the Leadforce pipeline stage names differ from Salesforce's default stage set, we create a custom Sales Process and map each Leadforce stage to a corresponding Salesforce stage with adjusted probability percentages.

Leadforce pipeline stages become Salesforce Opportunity stages within a custom Sales Process. We preserve the original stage names and order as a custom field lf_original_stage__c for reporting continuity. Stage probabilities migrate from Leadforce's stage configuration to Salesforce StageProbability values, rounded to the nearest integer percentage.

Leadforce Activities (calls, emails, meetings, tasks) map to Salesforce Task records with TaskSubtype set per activity type (Call, Email, Meeting). Activity timestamps preserve as ActivityDate, activity type preserves as TaskSubtype, and description text migrates to Task Description. Owner resolution uses email matching against the Salesforce User table.

Leadforce Notes attached to Leads or Deals migrate to Salesforce Note records linked via ContentDocumentLink to the parent record (Lead, Contact, Account, or Opportunity). Note body preserves as rich text, creation timestamp migrates as CreatedDate, and author attribution resolves via email-to-User lookup.

Leadforce file attachments require separate file extraction from CSV exports (where embedded as base64 or linked URLs) and re-upload to Salesforce as ContentVersion records attached via ContentDocumentLink to the parent record. We extract file names, types, and content during the export phase, upload to Salesforce via the Connect API, and link to the corresponding Lead, Deal, or Account record.

Leadforce Proposals generated from Deals migrate to Salesforce Quote records if the destination org has Quote enabled (Professional tier and above). Proposal line items migrate as QuoteLineItems with Product2 reference resolved. Where the destination Salesforce edition does not include native Quotes, we reconstruct proposal data as Opportunity Line Items or as a structured attachment.

Leadforce Invoice records linked to Deals migrate as structured financial data. We preserve invoice number, date, line items, amounts, and payment status. Invoices without a native Salesforce equivalent become a custom Invoice__c object with line items as Invoice_Line_Item__c records, or are appended to the parent Opportunity as historical financial notes.

Leadforce Owner and user assignments map to Salesforce User records resolved by email match. We extract every distinct owner referenced on Lead, Deal, Activity, and Note record and match against the destination Salesforce org's User table. Missing Users go to a reconciliation queue for the customer's admin to provision before record import resumes.

Leadforce custom fields on Leads and Deals require manual discovery via screen-share (no API schema enumeration exists). We document each custom field's name, data type, and sample values, then create matching Salesforce custom fields in the destination org before migration. Data type mapping includes Leadforce text to Salesforce Text, Leadforce number to Salesforce Number (with precision/scale), and Leadforce date to Salesforce Date.

Leadforce pipeline stage configurations (names, order, probabilities) map to a Salesforce Sales Process with custom stage entries. We configure the Sales Process in the destination org before importing any Opportunities so that stage assignments are valid at the moment of insert.