Migrate from Zurple to HubSpot

Zurple contact records map directly to HubSpot contacts. Every standard property — name, email, phone, address — creates a matching HubSpot contact property. OrphanedZurp contacts without a primary company land in HubSpot as standalone contacts; your team can associate them with HubSpot companies after migration if needed.

Zurple's unified contact model must split across HubSpot's Lead and Contact objects. Contacts inZurp with a lifecycle or lead status indicating active buyer/seller intent route to HubSpot contacts. Early-stage leads not yet qualified map to HubSpot leads so your sales team can work the pipeline before contacts are created in HubSpot.

Zurple company records map to HubSpot companies. Company name, domain, industry, and address properties translate directly. Where Zurp stores a parent-company hierarchy, HubSpot's Parent Company field preserves the structure. Multi-contact companies collapse cleanly — each contact in HubSpot links to one primary company via the Company property.

Zurple real-estate deals map to HubSpot deals. Transaction amount, close date, deal owner, and deal stage all have direct property equivalents in HubSpot. Your existingZurp pipeline name becomes the HubSpot pipeline name; eachZurp stage maps to a corresponding stage in that pipeline. Deal names from Zurp carry forward so reports reflect the original transaction description.

If yourZurp account uses named deal pipelines, eachZurp pipeline creates a HubSpot pipeline with matching stage names. The mapping plan lists eachZurp stage and its destination HubSpot stage so your team can validate the translation before the full migration runs. Multi-pipelineZurp accounts generate multiple HubSpot pipelines in the same process.

Zurple's lead status pick-list values map to HubSpot's lifecycle_stage contact property values. We preserve the exactZurplabel in HubSpot's pick-list so reporting shows the same stage names. WhereZurplifecycle stages differ from HubSpot's defaults, we create custom lifecycle values to match yourZurphierarchy exactly before importing records.

Zurple's numeric lead score has no native HubSpot equivalent outside of HubSpot's premium predictive scoring add-on. We create a custom number field (Zurp_Lead_Score__c or the equivalent in HubSpot) and migrate the existingZurpscore so your team retains the historical signal. Rebuying or redefining scoring logic in HubSpot is a post-migration step we document in the rebuild plan.

Zurple task records — call logs, follow-up reminders, and to-do items — map to HubSpot tasks. Task subject, due date, completion status, and owner all migrate. Original timestamps are preserved in HubSpot's Created Date and Last Modified Date fields so activity history reflects when each action was recorded inZurp.

Zurple tracks email opens and replies as engagement records on the contact. These become HubSpot engagement logs linked to the contact record. Subject lines, timestamps, and engagement type migrate so your HubSpot timeline shows the full email interaction history from theZurp period. HTML formatting fromZurp emails is preserved where possible.

Zurple's Conversations feature stores behavior-triggered message history — the sequence of automated emails and SMS a lead received — as a structured log on the contact. HubSpot has no equivalent native object. We preserve the conversation summary as a custom multi-line text property on the HubSpot contact so your team can reference it manually. The rebuild plan documents theZurp sequence logic for reconstruction in HubSpot workflows.

Zurple links contacts to MLS listings via a listing-ID property that tracks which property a lead is associated with. HubSpot has no native listing association field. We create a custom text property (MLS_Listing_ID__c or similar) on the HubSpot contact and populate it fromZurp so the association is preserved for reference, though linking to a full HubSpot property database requires a separate rebuild.

Zurple user records map to HubSpot users by email address. The migration flags anyZurp owner without a corresponding HubSpot user so your team can create the HubSpot user first or assign their records to a fallback owner. Owner resolution happens before records land in HubSpot so no contact or deal is orphaned during the migration.

AnyZurp custom contact, company, or deal properties — beyondZurp's standard fields — require HubSpot custom property creation. We auditZurp's full property list during scoping, create the matching HubSpot custom properties before migration, and validate that all custom data lands in the correct fields. Custom property count is a primary driver of migration scope and price.