Migrate from Ready_ to Salesforce Sales Cloud

Ready_ Contact records map directly to Salesforce Contact. Standard fields (FirstName, LastName, Email, Phone, MailingAddress) migrate directly. Custom properties on contacts (text, number, date, picklist types) map to Salesforce custom fields that we pre-create in the destination org before import. Email serves as the dedupe key during import to prevent duplicate Contact records.

Ready_ Company records map to Salesforce Account. Firmographic data (name, domain, industry, employee count) migrate directly. Account is created before Contact import so that the AccountId lookup on Contact is satisfied at insert time. The Company domain maps to the Account Website field and is used as the dedupe key alongside Account Name.

Ready_ Deal records map to Salesforce Opportunity. Deal amount maps to Amount, expected close date maps to CloseDate, and deal name maps to Name. The owner assignment resolves via Team Member ID-to-email translation to a Salesforce OwnerId. The Pipeline and Stage from Ready_ map to Salesforce Record Type, Sales Process, and StageName through the mapping table built during scoping.

Ready_ Pipelines (named deal groupings with custom stages) map to Salesforce Record Types on Opportunity. Each Pipeline becomes a Record Type with its own Sales Process that whitelists the relevant Stage values. This allows multi-line-of-business teams to maintain separate pipeline views without stage value collision across the org.

Ready_ Stage names and sequence order within each Pipeline map to Salesforce Stage values with associated probability percentages. We extract the full stage configuration from Ready_ during scoping, build a mapping table, and deploy the stages to Salesforce before Opportunity import. Stage probability percentages round to the nearest integer Salesforce allows.

Ready_ Team Members represent users and are the owner reference on Deals and Activities. We extract Team Member records (name, email) and match by email against the destination Salesforce User table. Any Team Member without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. This two-step resolution prevents silent ownership gaps in migrated Opportunities.

Ready_ call activities map to Salesforce Task with TaskSubtype=Call. Call disposition, duration, and notes transfer to custom Task fields. The WhoId on Task points to the resolved Contact; WhatId points to the related Opportunity if the call was logged against a Deal. ActivityDate preserves the original timestamp to maintain timeline ordering.

Ready_ email activities map to Salesforce EmailMessage (the email content) linked to a Task (the activity timeline entry). The WhoId on Task points to the Contact; the EmailMessage WhoId links to the same Contact. Email body and subject transfer directly. If the email was associated with a Deal in Ready_, the WhatId on both Task and EmailMessage points to the resolved Opportunity.

Ready_ task activities map directly to Salesforce Task with Status, Priority, Subject, and ActivityDate preserved. Task assignment migrates by resolving the Ready_ Team Member ID to Salesforce OwnerId via the User mapping. If the task was linked to a Deal, WhatId points to the resolved Opportunity.

Ready_ Notes are standalone records attached to Contacts or Deals. They migrate to Salesforce Note objects linked via ContentDocumentLink to the parent Contact or Opportunity. Note body transfers as plain text; any attachments transfer as separate ContentDocument records linked to the same parent record.

Ready_ custom fields on Contacts (text, number, date, picklist) require pre-creation of matching Salesforce custom fields before migration. We extract the field definition (API name, data type, picklist values) during scoping and create the corresponding fields in Salesforce during schema setup. Custom property values then load into the mapped fields during Contact import.

Ready_ custom fields on Deals map to Salesforce custom fields on Opportunity. We extract the field schema, create matching Opportunity custom fields in Salesforce (with appropriate field types), and load values during Opportunity import. Custom fields that reference other objects use Salesforce lookup field types with ID resolution at migration time.

Ready_ custom fields on Companies map to Salesforce custom fields on Account. Field types (text, number, date, picklist) translate directly. We pre-create the Account custom fields during schema setup so that Company import maps values on the first pass rather than requiring a post-import field addition.