Migrate from Convertkit to HubSpot

ConvertKit subscribers map directly to HubSpot contacts. Email address is the unique identifier. Each subscriber becomes a contact record with all standard properties (name, email, created date) preserved. Subscribers without email addresses cannot migrate. We also validate email format and check for duplicates before import to avoid overwriting existing contacts.

ConvertKit tags are free-form strings applied N-to-N to subscribers. We map tag values to either HubSpot contact properties (when tag represents a trait like 'customer_type') or HubSpot static lists (when tag represents a segment for targeted sends). Tag frequency data preserved as property values.

ConvertKit custom fields map 1:1 to HubSpot contact properties. Property type (text, number, date, dropdown) is preserved. Maximum 140 ConvertKit custom fields; HubSpot allows 500+ contact properties by default. Field key becomes the property name in HubSpot. We also verify that picklist values match HubSpot's allowed options before migration.

ConvertKit forms do not migrate as functional HubSpot forms. We export form field names, submission logic, and styling as a rebuild reference. HubSpot forms are created manually or via HubSpot's form builder. Form-field-to-contact-property mapping documented for recreation. We also include screenshots of original forms to aid designers in recreating the look and feel.

ConvertKit landing pages do not transfer to HubSpot landing pages. HTML structure and content exported as reference documents. Landing pages must be rebuilt in HubSpot's CMS or external tools. We map page URLs and form associations for redirect planning. We also capture meta tags and SEO titles for each page to preserve search visibility after migration.

ConvertKit sequences (automated email drip series) cannot be exported as functional HubSpot sequences or workflows. Email content exported as HTML documents. Sequence logic (triggers, delays, conditions) documented for manual rebuild in HubSpot Sales Hub sequences or Operations Hub workflows. We also provide timing diagrams and decision trees to clarify each step during the rebuild process.

ConvertKit broadcasts (one-time email sends) do not migrate as live HubSpot campaigns. Broadcast content, subject lines, send dates, and audience lists exported as reference. We preserve the broadcast history as a custom property on each contact (last broadcast received, broadcast names).

ConvertKit products (digital goods, paid newsletters) map to HubSpot products. Product name, price, and description transferred. HubSpot product records can be linked to deals if your team uses the e-commerce or quote features. We also ensure product images and URLs are included for reference in HubSpot's product library.

ConvertKit purchase events merge into HubSpot deal and line item records. Each purchase becomes a deal linked to the contact, with product details as line items. Deal stage set to 'Closed Won' by default. Purchase timestamps preserved on the deal record.

Original subscriber creation timestamps preserved as a HubSpot contact property (Original_Subscriber_Created_Date__c). HubSpot's native CreatedDate reflects migration time; the custom property preserves the original ConvertKit date for reporting continuity. We also update any date-based workflows or reports to reference the custom property, ensuring historical trends remain accurate after migration.

ConvertKit unsubscribe flags map to HubSpot's contact email opt-out property. Unsubscribes transfer as active opt-outs so HubSpot respects existing suppression. Re-subscribes in ConvertKit before migration cutover are honored. We also verify opt-out timestamps are recorded for compliance reporting and audit trails.

ConvertKit API credentials and account configuration do not map to HubSpot equivalents. We export account settings (from name, reply-to address, sender branding) as a checklist for HubSpot account configuration. Private apps in HubSpot created separately. We also document IP whitelisting and webhook URLs for future integration setup.