Migrate from Delta Sales CRM to Salesforce Sales Cloud

Delta Contacts map directly to Salesforce Contact. The standard fields (Name, Phone, Email, Mailing Address) align 1:1. We extract all custom fields on the Contact object and create matching custom fields in Salesforce before import. The contact-company linkage is preserved via the AccountId lookup resolved at import time from the Delta Company mapping.

Delta Companies map to Salesforce Account. The company name becomes the Account Name, website becomes the Website field, and any industry or type fields map to their Salesforce equivalents. Account is imported before Contact so that the AccountId lookup is satisfied at Contact insert time. Companies without a linked contact are migrated as Account-only records.

Delta Leads map to Salesforce Lead. Lead status, source, owner, and any custom fields migrate directly. If the customer's Delta account uses Leads primarily as an unqualified pipeline stage (rather than converting to deals), we discuss whether to import as Salesforce Lead or merge into Contact during scoping. Any lead score or qualification data stored in Delta custom fields migrates to custom fields on Salesforce Lead.

Delta Deals map to Salesforce Opportunity. Deal name becomes Opportunity Name, amount maps to Amount, close date maps to CloseDate, stage maps to StageName, and probability maps to Probability (rounded to Salesforce-allowed integer values). We resolve AccountId and OwnerId from the parent-company and owner mappings before Opportunity insert.

Each Delta pipeline becomes a Salesforce Record Type on Opportunity, with a corresponding Sales Process that whitelists only the relevant stage values. Pipeline stage names map to Salesforce StageName values in the order defined in Delta. If Delta uses multiple pipelines for different business units, each pipeline maps to a distinct Record Type in Salesforce.

Delta Activities (Tasks, Meetings, Calls, and Reminders) map to Salesforce Task and Event objects. Call activities become Task with TaskSubtype=Call; meeting activities become Event with attendee relations; standard tasks remain Task. Activity date, assignee, status, and description migrate directly. We resolve WhoId (Contact or Lead lookup) and WhatId (Opportunity or Account lookup) from the parent-record mappings at migration time.

Delta Products map to Salesforce Product2. Product name, SKU, description, and pricing fields migrate to Product2 Name, ProductCode, Description, and a custom price field. Standard Pricebook entries are created in Salesforce before Line Items are imported so that the Pricebook2 reference is satisfied at Line Item insert.

Delta Invoices have no direct Salesforce standard object equivalent in Sales Cloud Essentials or Professional without additional modules. We create a Delta_Invoice__c custom object with fields for invoice number, date, amount, status, and linked Contact and Account lookups. Invoice line items become child records of Delta_Invoice__c. If the customer has Salesforce Billing or a third-party invoicing tool, we discuss integrating the custom object with that module.

Delta Payment records map to a Delta_Payment__c custom object linked to Delta_Invoice__c (the invoice object above). Payment amount, date, method, and status migrate to custom fields. If the customer uses Salesforce Opportunity with invoice-to-cash automation, payments can alternatively map to Opportunity as field updates, but the standard approach for Delta-sourced payment history is a custom object.

Delta custom fields across all objects map to Salesforce custom fields of equivalent data type. Text fields map to Text, number fields to Number, date fields to Date, picklist fields to Picklist. We create the Salesforce custom field schema before any data import so that the target fields exist and validation rules can be tested against migrated data. The customer confirms naming convention preference (display label vs API name) during scoping.

Delta Beat Plans are field-force routing structures assigning route sequences to reps with customer visit order, scheduled dates, and visit status. There is no standard Salesforce equivalent. We create a Delta_Beat_Plan__c custom object with fields for plan name, rep owner (User lookup), scheduled date, and a child Delta_Beat_Visit__c object for individual visit records with customer lookup, visit order, planned time, actual time, and visit notes. The customer uses the standard Salesforce mobile app for visit logging post-migration.

Delta file attachments are exported as binary blobs with their associated record ID. We upload them to Salesforce as ContentVersion records linked via ContentDocumentLink to the parent Contact, Account, Opportunity, or custom object. Large attachment batches (over 5,000 files) require chunked upload with the Salesforce Content API to avoid batch size limits. We confirm file volume during scoping.

Delta users referenced on records (deal owner, task assignee, activity owner) are resolved by email match against the Salesforce destination org's User table during migration. Any Delta Owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. We do not create Salesforce Users; that is an admin action gated by license assignment.