Migrate from Convertkit to Freshsales

ConvertKit subscribers map directly to Freshsales Contacts on a one-to-one basis. Subscribers without an email address cannot be migrated since Freshsales mandates an email field for Contact creation. Original subscriber create dates are preserved as a custom datetime field because Freshsales sets the CreatedAt timestamp at migration time rather than preserving the original value.

Subscribers tagged with a lifecycle-style tag (such as 'buyer', 'customer', or similar indicating a closed-won relationship) are routed to Freshsales Lead for follow-up CRM capture and sales pipeline entry. Most ConvertKit subscribers without a purchase tag route directly to Contact under the same classification logic, ensuring the migration distinguishes between customer records and audience members.

ConvertKit custom fields of type text, number, date, checkbox, and dropdown map to Freshsales custom fields of the equivalent type. Freshsales Pro and Enterprise plans support Advanced Custom Fields; Growth plan supports Basic. The plan tier on the destination account determines which field types are available.

ConvertKit tags are stored as a custom multi-select text field on the Freshsales Contact. The tag comma-separated list is preserved verbatim. ConvertKit's dynamic segment membership (tags applied by behavioral triggers) cannot translate to Freshsales dynamic lists — those must be rebuilt as Freshsales Smart Lists manually.

ConvertKit form field definitions map to Freshsales custom field definitions (the field label and type carry over). The form itself — its layout, visual styling, and thank-you page — must be rebuilt in Freshsales Forms manually. Form submission records are preserved as notes or custom activity records.

ConvertKit Products (digital products, paid newsletter plans, Tip Jar offerings) map to Freshsales Products. Product name, pricing, and description carry over. Freshsales Products link to Deals via Deal Line Items — if ConvertKit orders need deal-level tracking, a Deal object must be created first, then the product linked.

ConvertKit broadcast email history does not map to a Freshsales object. Freshsales has no broadcast or campaign-send equivalent at the Contact level. Email engagement history from ConvertKit can be preserved as custom activity notes or linked to a custom object, but the broadcast campaign logic must be rebuilt in Freshsales Workflows or Freshmarketer Journeys.

ConvertKit sequences — multi-step drip email automations — have no native equivalent in Freshsales CRM. Freshsales Sales Sequences (available on Pro and Enterprise plans) handle outbound cadences but use a different trigger model. The sequence structure must be exported as a reference document and rebuilt in Freshsales manually.

ConvertKit automation rules (visual automation builder, trigger-based actions) do not transfer. Freshsales Workflows (available on all plans with different complexity limits) use a different event-action model. FlitStack AI exports the automation definitions as a JSON reference file for the Freshsales admin to rebuild.

Freshsales sets the CreatedAt field automatically when records land during migration, which reflects the migration timestamp rather than the original subscription date. The original ConvertKit subscription date is stored as a custom datetime field so reporting on subscriber tenure remains continuous after go-live and historical engagement analysis can proceed without data gaps.

Email serves as the primary identifier in both ConvertKit and Freshsales platforms. Freshsales mandates an email address for Contact creation, making it a required field. Subscribers with invalid, malformed, or missing email addresses are flagged during the pre-migration validation phase and excluded from the standard migration run to prevent data quality issues in the destination system.

ConvertKit Creator Profiles and landing pages are considered website assets rather than CRM data, which means they exist outside the scope of contact and account record migration. They cannot be migrated to Freshsales since the platform does not host landing page content. Teams should plan to set up new landing pages using Freshforms or a separate CMS solution after the CRM migration completes to maintain lead capture capabilities.