Migrate from Convertkit to Nutshell

ConvertKit subscribers map directly to Nutshell People records. We pull first name, last name, email address, and state (subscribed/unsubscribed/cancelled) from the subscriber record and create a corresponding Person in Nutshell. The original opt-in date migrates as a custom datetime field for compliance continuity.

ConvertKit subscribers flagged as leads in your workflow (e.g., via a 'lead' tag or form type) can route to Nutshell Leads alongside or instead of People records. We apply your specified tag-to-Lead routing rule — if a subscriber carries a specific tag, they land as a Nutshell Lead rather than a Person.

ConvertKit tags migrate as freeform tags on Nutshell People records. Each unique tag value becomes a tag on the Person. Nutshell's tag system supports unlimited tag values per Person, matching ConvertKit's N:1 subscriber-to-tag relationship. Tag-based segmentation in Nutshell uses these migrated tags as the filter criteria.

ConvertKit tag categories (groups of related tags used for segmentation) map to Nutshell Segments built by filtering on multiple tag values and field conditions. We document the original tag category membership so your Nutshell admin can rebuild segments using the same logical structure.

ConvertKit subscriber custom fields map to Nutshell custom fields on Person, Company, or Lead depending on their content domain (e.g., a custom field storing a company name maps to a custom field on Company). Up to 140 ConvertKit custom fields are supported. Nutshell field types must be matched — address field types cannot be imported from CSV, so those custom fields are flagged for manual review.

ConvertKit form submissions do not have a direct Nutshell equivalent because Nutshell does not have a native form response object. We migrate each form submission as a Note attached to the corresponding Person record, capturing form name, submission timestamp, and the fields submitted. This preserves the submission history for audit purposes.

ConvertKit Products and purchase records do not map to a standard Nutshell object natively. We create a Nutshell Deal for each paid purchase, with the product name as the Deal name, purchase amount as the Deal value, and the subscriber as the associated Person. Pipeline stage is set to a 'Closed Won' equivalent stage to reflect completed purchases.

ConvertKit Sequences (automated email funnels with branching logic, time delays, and conditional paths) have no migration path to Nutshell. They must be rebuilt in Nutshell's email sequence and automation tools. We export the full sequence definition — steps, triggers, delays, and conditional rules — as a structured specification document your Nutshell admin can use for rebuild.

ConvertKit Broadcast history (past sends) can be referenced in Nutshell as notes or custom fields, but the broadcast content itself does not migrate as a live Nutshell email campaign. Active broadcast logic (scheduled sends) must be rebuilt as Nutshell email campaigns. We map the subscriber lists used in each broadcast to Nutshell People segments for reuse.

ConvertKit Creator Profile pages encompass landing pages, recommendation cards, product storefronts, and lead magnets hosted within the ConvertKit ecosystem. These platform-specific assets have no direct Nutshell equivalent, as Nutshell is a CRM rather than a content-hosting platform. Creator Profile configuration — including page layouts, storefront product listings, recommendation link structures, and media embed references — is exported as a comprehensive reference document. Your team will need to evaluate third-party hosting solutions (such as a website builder or dedicated storefront platform) to recreate these assets outside ConvertKit, using the exported configuration as the source blueprint for rebuild.

ConvertKit does not natively store large file attachments on subscriber records in the same way a CRM does. Any file assets stored in ConvertKit (e.g., via form attachments or product files) must be exported and re-hosted separately — Nutshell does not have a native file attachment object equivalent to a CRM attachment system.

ConvertKit subscriber state transitions (subscribed, unsubscribed, bounced, cancelled) are preserved as state changes on the Nutshell Person record using the state field. Historical state-change timestamps migrate as a custom datetime field so reporting can show the full opt-in and opt-out timeline for compliance records.