Migrate your CRM Service data

Standard object with comprehensive field set including billing/shipping addresses, industry classification, annual revenue, and ownership hierarchy. We map Accounts directly to the destination CRM's Companies/Organizations object preserving name, industry, and address fields.

Core contact record linked to Accounts via lookup relationship. Contains email, phone, title, department, and lifecycle stage. We preserve Contact-to-Account linkage during migration by matching on account external IDs or names.

Deals pipeline object with stage, amount, close date, probability, and forecast category. We map Opportunity fields to Deals in destination CRMs, preserving stage progression history and amount data.

Lead object available on Sales Hub Enterprise edition only, introduced in 2023. Where destination lacks a separate Lead object, we merge Leads into Contacts and preserve Lead_Status as a custom contact property.

Custom objects carry the __c suffix and can have independent schemas, relationships, and page layouts. We export full custom object schemas including lookup relationships, custom fields, and validation rules. Mapping requires field-by-field alignment with destination.

Pipeline configuration is org-specific with custom stage names, probabilities, and automation triggers. We map stage names and probabilities to destination pipeline stages but recommend rebuilding stage-based automations post-migration.

Tasks and Events represent engagement history. Activity data often includes open activities that should not be migrated. We export completed activities and map them to the destination's activity/timeline object, excluding incomplete tasks that may create confusion.

Files and Attachments stored in Salesforce require separate export via ContentDocument or Attachment objects. File sizes and storage limits vary by edition. We export files to a staging location and re-upload to destination, preserving content document links where possible.

Custom reports and dashboards contain destination-specific data references and cannot be imported into other platforms. We export report metadata as documentation but do not migrate report definitions. Clients should rebuild reports post-migration using migrated data.

Automation logic including Workflow Rules, Process Builder flows, and Flow definitions do not transfer between CRM platforms. We document existing automations as part of migration scoping but do not export automation rules. These must be rebuilt in the destination system.

User records represent team members with role, profile, and territory assignments. User export requires mapping to destination users by email. Inactive users may be excluded or archived depending on data retention requirements.

Multi-select picklist values and tag assignments require value-level mapping. We export tag values as-is and map them to destination tag/labels fields, consolidating where destination has fewer allowed values.

Campaign object tracks marketing initiatives with member status and response data. Campaign-to-Contact associations are preserved via member records. We export campaign history including member responses for attribution reporting.

Case object from Service Cloud contains status, priority, origin, and associated contacts. Case migration is scoped based on open versus closed status. We recommend excluding very old closed cases unless regulatory retention requires otherwise.