Migrate from Nurture to HubSpot

Direct map. Nurture contacts migrate to HubSpot contacts preserving original email, phone, name, and address fields. Owner resolution matches Nurture owner email to HubSpot user email; any unmatched owners are flagged for your team. Contacts without a primary venue are linked to a default HubSpot company, preventing orphan records in reports.

Nurture venues migrate to HubSpot companies, preserving venue name, address, capacity, and style as company properties. Any venue‑specific contacts (e.g., venue manager) are imported as associated company contacts. If Nurture contains parent‑child venue relationships, we replicate the hierarchy using HubSpot’s Parent Company field, and any circular references are flagged before migration. This ensures multi‑location venue groups appear correctly in HubSpot reporting.

Nurture bookings map to HubSpot deals. Booking status (inquiry, proposal, booked) maps to HubSpot deal stage. Package tier, guest count, event date, and venue association migrate as deal properties and company association. Won deals represent confirmed bookings; lost deals represent declined inquiries.

Nurture tasks are imported as HubSpot tasks, preserving the original due date, task description, and owner assignment. We also store the original create timestamp as a custom datetime field. If a Nurture task references an owner without a HubSpot account, the task is flagged for your team to assign a fallback owner before migration. Task status (open, completed) maps directly to HubSpot’s task state, preserving the original open/closed workflow.

Nurture notes are imported as HubSpot notes and attached to the parent contact, company, or deal record using HubSpot’s association API. Original note body, timestamps, and owner information are preserved, and rich‑text formatting (bold, bullets, links) is retained where supported. If a note contains embedded images, we store the media URL as a custom field and link it to the note. This keeps your historical client communications searchable and intact.

Nurture date fields such as wedding_date migrate to HubSpot date properties, stored in ISO 8601 format (YYYY‑MM‑DD). The date property is attached to the deal record, enabling timeline filtering and reporting by event date. During the planning audit we verify that all Nurture date fields are correctly typed as dates in HubSpot, preventing accidental mapping to text properties.

Nurture numeric properties such as guest_count migrate directly to HubSpot number properties on the deal record. We validate that values contain only digits; any that include text are cleaned or stored as a custom text field after your approval. The number property is then available for filtering, sorting, and calculations in HubSpot’s pipeline and reporting views, preserving the original guest count data without transformation.

Nurture pick‑list values for package_tier are mapped value‑by‑value to HubSpot option sets. We generate a mapping table pairing each Nurture label with the corresponding HubSpot option, and your HubSpot admin approves it before migration. If a Nurture option does not exist in HubSpot, we create it in the appropriate option set, ensuring consistent package tier data in filters and reports.

Nurture booking_status pick‑list values map to HubSpot deal stage values via a documented value‑mapping table. Typically, inquiry, consultation, and proposal map to early pipeline stages, booked maps to Closed Won, and lost inquiries map to Closed Lost. Stage‑change timestamps are preserved as custom datetime fields, so you can view when each status transition occurred in HubSpot’s timeline.

Nurture email activities are imported as HubSpot email engagements, preserving the original timestamp, subject, body, and any attachment URLs. Each email is linked to its primary contact, and if the message references a company or deal, those associations are created as well. We map the engagement type to HubSpot’s email format so the messages appear correctly in the contact timeline. This keeps your historical email communication searchable and intact.

Nurture sequences and inquiry‑to‑booking automations are configuration objects that have no direct counterpart in HubSpot, so they do not migrate. We export every Nurture workflow definition—including triggers, conditions, step order, time delays, and email content—as a structured reference document. Your HubSpot admin can use that document to recreate equivalent automation in HubSpot’s Workflows tool, Sales Hub Sequences, or other automation features.

Nurture owner records resolve by email match to HubSpot users. Unmatched owners are flagged before migration — your team either invites them to HubSpot first or assigns their records to a fallback HubSpot owner. No record lands without an owner.