Migrate from Ready_ to Twenty CRM

Ready_ Contacts map to Twenty's Person object. Standard fields (name, email, phone, address) migrate directly. Custom properties on Ready_ Contacts (text, number, date, picklist) map to matching Twenty custom fields, which we pre-create via the Twenty Metadata API before record import. The Person object in Twenty also stores avatar, job title, and LinkedIn URL where those fields exist in Ready_.

Ready_ Company records map to Twenty Company. The domain field from Ready_ maps to Twenty's website URL, and the company name is the dedupe key during import. Industry, employee count, and annual revenue custom fields migrate as Twenty custom fields. Related contacts are linked via the Person-Company association in Twenty after both objects are created.

Ready_ Deals map to Twenty Opportunity. The deal value, expected close date, and owner migrate directly. Pipeline and Stage assignment requires the explicit mapping table built during scoping because Ready_ allows fully custom pipeline and stage names with no enforced convention. Closed-Lost and Closed-Won statuses from Ready_ map to Twenty's Opportunity status values.

Each named Pipeline and Stage in Ready_ becomes a stage row in Twenty's Opportunity pipeline. We extract the stage name, sequence order, and any custom probability values during scoping, then configure the matching Twenty pipeline before migration. Stage ordering is preserved by setting the sort order value in Twenty.

If the Ready_ account uses multiple named Pipelines, we create a corresponding number of Pipelines in Twenty and map each one explicitly. Ready_ pipeline assignment on each Deal is resolved to the correct Twenty Pipeline ID during import using the mapping table built during scoping.

Ready_ Activities (calls, emails, tasks) map to Twenty Timeline Entries linked to the Person or Opportunity record. Activity type from Ready_ maps to the type discriminator in Twenty's timeline schema. Timestamps and notes content preserve; activity owner migrates via email-to-User resolution. Activity types in Ready_ may not map 1:1 to Twenty's event types, so we document the mapping and supply type placeholders for any unmapped activity kinds.

Ready_ Notes attached to Contacts or Deals migrate as Twenty Timeline Entries with the note body in the content field and the linked Person or Opportunity as the parent. We resolve the linked record type and ID at migration time to ensure the note appears in the correct timeline in Twenty.

Ready_ Team Members represent users and are referenced by internal ID on Deals, Activities, and Notes. We extract all Team Member IDs, resolve them to email addresses, and match those emails to existing Twenty User records. Any Team Member without a matching Twenty User enters a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignments on migrated records resolve to the Twenty User ID.

Ready_ custom fields on Contacts, Companies, and Deals (text, number, date, picklist) map to Twenty custom fields of the equivalent type. We pre-create the custom field definitions in Twenty via the Metadata API before any records are imported, ensuring the target schema exists before data is written. Picklist values from Ready_ migrate as select options in Twenty.

If the Ready_ account uses the maximum custom field allowance and requires standalone related-record structures, Twenty's custom object model provides this natively. We create the equivalent custom object in Twenty with the same field types and lookup relationships, then migrate any associated records. This step requires schema design during scoping and is scoped separately from the core object migration.