Migrate your Sales ERP data

Standard primary object for companies and organizations. Exposed via REST and Bulk API 2.0 with stable schema across editions. We map Accounts 1:1 in most migrations and preserve parent-account hierarchies via the ParentId field.

Standard object linked to Accounts via AccountId. We handle Contact-to-Account relationships, duplicate detection rules, and ownership assignment during migration. The Account Contact Relation object is used for multi-role contacts.

Core sales pipeline object. We preserve stage history, probability curves, and Opportunity Team Member assignments. Forecast categories require explicit mapping because they vary by org configuration.

Leads are a distinct object from Contacts. Where the destination CRM lacks a separate Lead concept, we merge Leads into Contacts and preserve Lead_Status and Lead_Source as custom Contact properties. Lead assignment rules require rule-to-rule mapping.

Order object stores fulfillment records linked to Accounts and Contracts. OrderItems represent line items. We map Order status transitions and preserve the Account-Order-Contract lineage through field-level references.

Contract records link to Accounts and drive Order fulfillment eligibility. Start and end dates, status, and renewal terms are standard fields. We preserve Contract-Order associations and flag contract milestones for downstream systems.

Product2 defines sellable items with IsActive flags and product codes. Standard object with stable schema. We map Products directly but validate that inactive products are flagged rather than silently dropped.

Links Products to Price Books with unit prices. Custom Price Books require explicit mapping. We validate that all products have at least one active price book entry in the destination or flag missing entries for review.

Service Cloud Cases are linked to Contacts and Accounts. Custom Case fields and entitlements require field-level mapping. We preserve Case-to-Contact relationships and escalate hierarchy when converting Cases to Accounts.

Marketing Campaigns and Campaign Members represent audience lists. Campaign Member statuses map differently across platforms. We handle Campaign hierarchies and flag Custom Campaign fields for explicit value mapping.

User object represents active Salesforce licenses. We map Users to destination owners and preserve Role and Profile assignments. Deactivated users are not migrated by default to avoid license waste in the destination system.

Custom objects created via Application Composer or managed packages are accessible via REST API with their API Name (ending in __c). We map custom object records and relationships but cannot apply custom saved searches since query parameters are unsupported for custom objects.

Attachments and Notes export as separate rows per parent record, not inline with the parent object. We handle them as distinct record types and flag multi-attachment-per-contact scenarios that may require file-to-record reassignment in the destination.