Migrate from Ready_ to HighLevel

Ready_ Contacts map directly to GoHighLevel Contacts. Standard fields (name, email, phone, address) migrate to matching GoHighLevel Contact properties. Custom fields on Ready_ Contacts are migrated to GoHighLevel Custom Fields on Contact, which we pre-create in the destination account before import. The contact's primary Company association in Ready_ resolves to a GoHighLevel Location record, and we link the Contact to that Location via the contact-location association. Email address serves as the dedupe key during import to prevent duplicate Contact creation.

Ready_ Company records map to GoHighLevel Companies with each Company receiving a primary Location. Ready_ fields for company name, domain, industry, and size map to GoHighLevel Company name, website, industry, and number of employees. If a Ready_ Company has multiple office locations, we create a Company record with multiple Locations under it and distribute the related Contacts accordingly. Company is created before Contact import so that the contact-location link is satisfied at insert time.

Ready_ Deals map to GoHighLevel Opportunities. The deal name, value, expected close date, and owner migrate to Opportunity name, amount, close date, and assigned user. Ready_'s deal stage name maps to a GoHighLevel Pipeline stage. Pipeline and stage names in Ready_ are user-defined and require explicit mapping per account; we collect the full pipeline configuration during scoping and build the mapping table before migration. Closed-won and closed-lost statuses from Ready_ map to GoHighLevel Won and Lost stages with any custom close reasons preserved as notes on the Opportunity.

Ready_ Pipelines and Stages are fully custom-named per account with no enforced convention. GoHighLevel Pipelines and Stages are also configurable. During scoping, we extract every pipeline and stage from Ready_ by name and sequence order, then create matching Pipelines and Stages in GoHighLevel. Stage probability values from Ready_ (if present) are entered as stage weights in GoHighLevel. This configuration step must complete before Deal records are imported because Opportunities in GoHighLevel require a Pipeline assignment.

Ready_ Activities (calls, emails, tasks) map to GoHighLevel Tasks and Notes. We map the activity type, timestamp, body content, and linked record. Call activities from Ready_ migrate as GoHighLevel Tasks with a call disposition note; email activities migrate as Notes attached to the Contact. The original activity timestamp is preserved on the Task or Note for timeline ordering. Activity types that do not map directly to GoHighLevel task types are stored as Notes with the original type label preserved.

Ready_ owner assignments on Deals and Activities reference Team Member IDs that have no meaning in GoHighLevel. We extract Team Members by name and email during the discovery phase, then match those emails to existing GoHighLevel users in the destination account. Any Team Member without a matching GoHighLevel user is held in a reconciliation queue for the customer's admin to provision before record import resumes. This two-step resolution prevents silent ownership gaps where Deals and Tasks land with no assigned owner.

Ready_ custom fields on Contacts, Companies, and Deals (types include text, number, date, and picklist) migrate to GoHighLevel Custom Fields on the equivalent object. For Ready_ custom fields that represent structured relationships rather than simple properties, we evaluate whether a GoHighLevel Custom Object is the appropriate destination. Custom Object creation requires a schema definition step before data import and may add one to three days to the migration timeline depending on relationship complexity.

Ready_ Notes attached to Contacts or Deals migrate to GoHighLevel Notes. The note body, creation timestamp, and linked record association are preserved. GoHighLevel Notes attach to the corresponding Contact or Opportunity via the internal ID resolved during import. We preserve the note creation date to maintain chronological ordering in the GoHighLevel activity timeline.