Migrate your Salesforce Sales Cloud data

The primary company/customer record in Salesforce. Standard fields (Name, Industry, Annual Revenue, Type) are stable and map cleanly. Parent-Account hierarchies must be sequenced — we import parent Accounts first, then children. Supports custom fields freely.

Person-level records linked to Accounts via a many-to-many Account Contact Relation junction object. We import Contacts after Accounts are committed and map the junction table as a second pass. Supports custom fields and direct Owner assignment.

Unqualified prospects tracked before conversion. Contains LeadSource, Status, Rating, and custom fields. Conversion creates an Account, Contact, and optionally an Opportunity — we handle both migrated Leads and their post-conversion artifacts.

The core deal record with Stage, Amount, Close Date, and Probability. Multi-currency and negative Amounts are supported natively. We import after Accounts exist; Opportunity Contact Roles and Opportunity Team Members are separate passes.

Support tickets with Status, Priority, Origin, and Contact/Account linkage. Supports custom fields and entitlement association. Cases with open Activities must have those Activities imported separately after the parent Case.

Marketing initiative containers with Budget, Status, and Type. Campaign Members track individual Contact or Lead responses. We import Campaigns first, then Campaign Members in batches against the Bulk API quota.

Legal agreement records with Start Date, End Date, Contract Term, and Status. Linked to an Account and optionally to a primary Contact. Contract Line Items are a separate object and require separate mapping.

Order records exist on top of Opportunities and Contracts. Status, Effective Date, and Order Products must all map correctly. If the org uses Advanced Order Management or Revenue Cloud, order lineage and related asset creation require additional handling beyond a standard flat import.

Products are the catalog items; Price Book Entries link them to Price Books with pricing. Opportunity Line Items reference Price Book Entries. We map Products first, then Price Book Entries, then Opportunity Products — a three-pass sequence. Custom pricing on line items requires field-level mapping.

Quote records linked to Opportunities, carrying line items and pricing. Quote Line Items reference Products and Price Book Entries. We import Quotes after Opportunities are in place and before finalizing order conversion.

Post-sale product ownership records linked to Accounts and Contacts. Serial Number, Status, Install Date, and Quantity map cleanly. Assets created automatically from Contracts or Orders require the parent records to exist first.

Fully supported via the Metadata API for schema discovery and the Bulk API / Composite API for data migration. Each Custom Object may have its own dependency chain — we audit relationships before sequencing the import. Naming conventions (MyObject__c) are preserved in the destination.

Tasks and Events are individual activity records linked to any Who or What object (Contact, Lead, Account, Opportunity). They do not exist in a hierarchy, but open Tasks against deleted parent records will fail to insert — we filter or flag these during validation.

Team member junction records that assign User IDs to an Account or Opportunity with a specific role. We import these after the parent Account or Opportunity and after all relevant User records exist in the destination. Sequential ordering by Team Member ID is not guaranteed, so we batch and upsert by External ID.