Migrate from Nurture to HighLevel

Nurture Contacts map directly to GoHighLevel Contacts. We preserve all standard fields (name, email, phone, address) and custom properties as GoHighLevel Contact custom fields. Email opt-in status from Nurture maps to GoHighLevel's contact.email_opted_out flag. The Contact is created after its parent Company so that the CompanyId reference is resolved at insert time.

Nurture Companies map to GoHighLevel Companies. Domain from Nurture becomes the GoHighLevel Company website field and is used as the deduplication key during import. Company is imported before Contact so that foreign-key references are satisfied before child record insertion.

Nurture Deals map to GoHighLevel Opportunities. Deal name, value, stage, owner, and expected close date transfer to the GoHighLevel Opportunity with pipeline stage mapped to a GoHighLevel pipeline stage. Deal custom properties migrate to GoHighLevel Opportunity custom fields.

Nurture pipeline stages are mapped to GoHighLevel pipeline stages within the designated GoHighLevel pipeline. Stage order and probability percentages transfer to GoHighLevel stage configuration. Each Nurture deal pipeline becomes a separate GoHighLevel pipeline if the customer has multiple pipelines configured.

Nurture Activity records of type call, email, meeting, and note map to GoHighLevel Task records with Task subtype set appropriately. Activity timestamps become Task due dates and completion dates. Activity notes and body content transfer to the Task description field. Call duration from Nurture activities is preserved as a custom Task field in GoHighLevel.

Nurture standalone Tasks map to GoHighLevel Tasks with status (open, completed), priority, due date, and assignee preserved. Owner assignment in Nurture resolves to the matching GoHighLevel user by email for task reassignment.

Nurture Owners map to GoHighLevel users by email match. Any Owner without a matching GoHighLevel user is placed in a reconciliation queue for the customer to provision before record import proceeds. Active and inactive status is preserved to indicate whether the user account should be active post-migration.

Nurture Contact custom properties migrate to GoHighLevel Contact custom fields. Field type mapping follows Nurture's property type (text to text, number to number, date to date, checkbox to checkbox). Custom fields are pre-created in GoHighLevel before Contact import begins.

Nurture Deal custom properties migrate to GoHighLevel Opportunity custom fields. These are created in GoHighLevel during the schema setup phase before any Opportunity data is loaded.