Migrate from Zymplify to HubSpot

Zymplify contacts migrate as HubSpot contacts. First name, last name, email, phone, job title, and address fields map directly. HubSpot requires an email address per contact — records without email are flagged for manual review before the migration runs. Original create dates are preserved as custom datetime properties since HubSpot's native createdate field reflects migration time.

Zymplify buyer-intent scores and intent-source flags (e.g., intent_strength, buyer_score, primary_intent_source) migrate to HubSpot custom number and text properties. These are static snapshots of Zymplify's Bombora data at migration time — they do not update post-migration unless you reconnect a third-party enrichment tool. We flag the last-enrichment timestamp for each record so your team knows data freshness.

Zymplify companies map directly to HubSpot companies. Company name, domain, industry, employee count, and annual revenue fields migrate directly. HubSpot's company object supports a primary domain field — we map Zymplify's primary website URL accordingly. Zymplify company hierarchies (parent-child relationships) map to HubSpot's parent company association.

Zymplify technographic data (installed technologies, software signals) migrates as HubSpot custom properties. HubSpot has no native technographic model — this data becomes static custom fields at migration time. Your team can connect a live technographic enrichment tool (e.g., BuiltWith, Clearbit) post-migration to refresh these values natively within HubSpot.

Zymplify deals migrate as HubSpot deals. Deal name, amount, stage, close date, and owner map directly. Each Zymplify pipeline maps to a HubSpot deal pipeline. Zymplify stage names map to HubSpot deal stage names via value mapping — we preserve stage-entry timestamps as HubSpot custom datetime fields for reporting continuity.

Zymplify deal-level custom properties migrate to HubSpot deal custom properties 1:1. If your Zymplify setup uses custom property sets specific to deal types (e.g., product_line, renewal_date, contract_terms), these map directly assuming HubSpot's custom property naming conventions are followed. We validate property type compatibility (text vs. number vs. date) during the field-level diff.

Zymplify email engagement records migrate to HubSpot's activity timeline on the associated contact or company. Each email record surfaces as a logged email activity with original timestamp, subject, and body preserved. HubSpot's activity timeline supports email, call, meeting, and note records — we map each Zymplify engagement type to its HubSpot activity type.

Zymplify call and meeting records migrate to HubSpot's activity timeline. Call duration, outcome (connected, voicemail, no answer), and meeting title map to HubSpot activity fields. Original timestamps and owners are preserved. HubSpot's engagement sequence model differs from Zymplify's cadence model — logged activities represent historical record, not future sequence steps.

Zymplify notes migrate as HubSpot notes attached to the parent contact, company, or deal record. Rich-text formatting is preserved where possible. Zymplify note timestamps and owner assignments map to HubSpot note metadata. Notes without an associated record are attached to the nearest parent contact or company based on the note's content context.

Zymplify workflow definitions (sequences, lead-routing rules, nurture paths) cannot be migrated. HubSpot has a separate Workflow engine for CRM automation and a Sequences tool for sales outreach — both require manual rebuilding. We export Zymplify workflow definitions as structured JSON and human-readable documents your HubSpot admin can use as a rebuild reference. Active enrolled contacts cannot be migrated mid-sequence — they need to be re-enrolled post-migration.

Zymplify owner IDs resolve to HubSpot users by email match. Each Zymplify user must have a corresponding HubSpot user account with the same email address before migration runs. Unmatched owners are flagged with their Zymplify owner record count so your team can either invite them to HubSpot or reassign their records to a fallback owner. We do not create HubSpot user accounts — that step must be completed by your HubSpot admin.

Zymplify file attachments associated with contacts, companies, or deals download and re-upload to HubSpot's File Manager. Files are linked back to their parent records in HubSpot. HubSpot's file storage limits apply (25MB per file by default). We flag any files exceeding HubSpot's size limit for manual handling before the migration commits.

Zymplify custom objects (if present in your plan) map 1:1 to HubSpot custom objects. Custom object associations that use a many-to-many model in Zymplify require a HubSpot association-junction object. We surface the full custom object schema during the pre-migration audit and include custom-object mapping in the field-level diff report.