Migrate from Convertkit to Salesforce Sales Cloud

Kit subscriber-count billing has no CRM equivalent in Salesforce

Kit bills based on total subscriber count — a flat number regardless of subscriber quality or engagement. Salesforce Sales Cloud has no equivalent concept. Subscriber count is not tracked as a field, report, or dashboard metric in Salesforce by default. If you are moving from Kit's subscriber-based pricing to Salesforce's per-seat model, the financial model changes entirely. We preserve the last-known Kit subscriber count as a custom field on the Account for audit reference, but the billing reconciliation must be handled outside the CRM.

Kit tag vocabularies can exceed Salesforce pick-list limits

Kit allows unlimited tags applied independently to each subscriber. Salesforce custom pick-list fields have a limit of 500 active values per field. If your Kit account has more than 500 distinct tags, a naive tag-to-pick-list mapping will fail. FlitStack surfaces the full tag vocabulary during discovery, flags tags exceeding Salesforce pick-list limits, and offers two alternatives: a custom junction object that stores tag values as related records, or a custom text field storing the full tag string — sacrificing native filtering in Salesforce reports for data completeness.

Kit Visual Automations and Sequences do not migrate and require manual rebuild

Kit sequences and Visual Automations are built on Kit's event model — triggers, conditions, time delays, and email sends tied to Kit's internal subscriber state. These constructs have no equivalent in Salesforce, which uses Flow with a completely different trigger, action, and condition architecture. Salesforce Flow cannot import Kit automation definitions. FlitStack exports Kit automation structure as a JSON summary and step-by-step outline. Your Salesforce admin must rebuild equivalent Flows from this reference. No automation logic transfers automatically.

Kit's flat subscriber model requires Account scaffolding in Salesforce

Kit stores contacts as a flat list with no required company or organization link. Salesforce Contacts require a lookup to an Account via AccountId — a Contact without an AccountId is technically possible but breaks most standard Salesforce reporting, page layouts, and sharing rules. FlitStack creates a placeholder Account named 'Kit Import — Individual' for Kit subscribers without an associated organization. If your Kit data has company name in a custom field, we can promote that to a real Account record and link contacts properly — this requires a mapping decision during planning.

Kit custom field API keys use a prefixed format that requires Salesforce naming adjustment

Kit's API returns custom field keys in the format ck_field_1_fieldname (e.g., ck_field_2_occupation). Salesforce custom field names follow the __c suffix convention (Occupation__c) and prohibit numeric prefixes in field labels, with a maximum label length of 40 characters. During migration, FlitStack strips the ck_field_* prefix, truncates if necessary, and maps the resulting label to Salesforce. If two Kit fields resolve to the same label after prefix removal, the tool appends a numeric disambiguator and flags the conflict for admin review before the data load proceeds.