Migrate from Ready_ to Freshsales

Ready_ Contacts map to Freshsales Contacts if the person is an active customer or sales-qualified prospect. If Ready_ stores unqualified prospect records, those map to Freshsales Leads. We determine the split using Ready_'s contact status or lifecycle property if present, otherwise default all to Contact and let the customer split post-migration. Email serves as the unique identifier for deduplication. Standard fields (first_name, last_name, email, phone, address) map directly.

Ready_ Company records map directly to Freshsales Account. The company name, domain, industry, and size fields map to Account_Name, Website, Industry, and Number_of_Employees. Related Contacts link to Account via the contact's account_id lookup that we resolve during Contact import.

Ready_ Deals map to Freshsales Deal. Deal_Name, Amount, Expected_Close_Date, and Owner map directly. The critical mapping is pipeline and stage: Ready_ allows custom-named pipelines and stages with no enforced convention, so we extract the full pipeline configuration during scoping and build a stage-mapping table to Freshsales' standard pipeline stages before import. Deals without a valid stage mapping are held in a reconciliation queue.

Ready_ Activities (calls, emails, meetings, tasks) require type-based routing to Freshsales. Call activities map to Task with Task_Subtype = Call. Meeting activities map to Event with Start_Time, End_Time, and Location preserved. Email activities map to Tasks with activity notes preserved in the description field. Standalone tasks map to Task. Activity timestamps are preserved for timeline ordering.

Ready_ Notes attached to Contacts or Deals map to Freshsales Notes linked to the corresponding Contact or Deal record. We resolve the parent record reference during import using the Contact or Deal ID. Note body and creation timestamp migrate directly.

Ready_ owner assignments on Deals and Activities reference Team Member IDs that do not persist across systems. We resolve Team Member IDs to email addresses during extraction, then match those emails to Freshsales User records by email lookup. Any Team Member without a matching Freshsales 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.

Ready_ custom fields on Contacts (text, number, date, picklist types) map to Freshsales custom contact fields. We extract the field definition (name, type, picklist values) during scoping, create matching fields in Freshsales before migration, then import values. Picklist values require explicit mapping if the label differs from the value in Ready_.

Ready_ custom fields on Companies map to Freshsales custom Account fields using the same extraction and pre-creation workflow as Contact custom fields. Field types are preserved (text, number, date, picklist).