Migrate from Knock CRM to Nutshell

Knock People map directly to Nutshell Contacts. All standard fields (name, email, phone, address) transfer 1:1. Each Knock Person must be linked to a Nutshell Account — FlitStack creates the Account first from the Knock Company, then links the Contact. Knock's guest card records (if stored as People) require a separate custom field mapping since Nutshell has no guest card object.

If Knock People records include unqualified prospects (not yet tied to a company or lease), they route to Nutshell Leads rather than Contacts. FlitStack splits by a Knock status field (e.g., 'Prospect' vs. 'Lease Signed') or by whether a Company association exists. Teams without a clear qualification status in Knock should decide which records go to Lead vs. Contact before migration runs.

Knock Company records map to Nutshell Accounts. The Account name, website, industry, employee count, and address fields transfer directly. Knock's parent/child company hierarchies map to Nutshell's Account Hierarchy via the Parent Account field. Multi-company associations on a single Knock Person collapse to one primary Account–Contact link in Nutshell.

Knock Deals map to Nutshell Opportunities. The deal name, amount, stage, close date, and owner transfer directly. Knock's deal-stage labels are mapped to Nutshell's pipeline stage values during migration — FlitStack generates the value-mapping table in the planning phase. Open and closed-won deals migrate with their original stage timestamps preserved as Nutshell custom fields.

Knock's multiple independent pipelines must map to Nutshell's single pipeline. Teams have two options: select one Knock pipeline as primary and drop the others, or consolidate all stages into one Nutshell pipeline. FlitStack delivers a pipeline consolidation plan as part of the pre-migration spec so Nutshell admins can pre-create the correct stage values before data lands.

Knock's custom properties on People records (e.g., 'referred_by', 'source_channel', 'apartment_interest') require Nutshell custom fields to be created before migration. Nutshell supports text, date, number, and pick-list custom field types. Multi-select Knock properties are flattened to pipe-delimited text in Nutshell. FlitStack lists every Knock custom property in the planning spec so Nutshell admins can pre-create fields.

Knock Company custom properties (e.g., 'property_type', 'unit_count', 'market_class') migrate to Nutshell Account custom fields. The same type-restriction note applies: Nutshell's pick-list fields are less flexible than Knock's. Teams should identify which Knock custom properties are business-critical vs. reference-only and prioritize creating Nutshell custom fields only for the former.

Knock's activity history (calls logged, emails sent, meetings scheduled) maps to Nutshell Tasks and Events. Call activities with disposition notes become Tasks with Type='Call'. Email activities become Tasks with Type='Email'. Meetings with start/end times become Nutshell Events. All original timestamps and owner assignments are preserved. FlitStack maps the activity type from Knock's activity.kind field to the corresponding Nutshell object.

Knock Notes with associated file attachments migrate to Nutshell Notes with linked Files. File size limits apply (Nutshell's default 25MB per file); files exceeding this threshold are flagged for manual re-upload. Rich-text formatting in Knock Notes is preserved as plain text or HTML in Nutshell Notes depending on the target field type available in the account's plan.

Knock's tagging system maps to Nutshell's native Tags. Tag names transfer verbatim. Nutshell applies tags at the record level (Account, Contact, or Opportunity). If Knock tags are used for complex segmentation logic, the team should audit which tag-to-segment mappings need to be rebuilt as Nutshell filters or custom reports.

Knock owner IDs are resolved by email match against Nutshell users. FlitStack generates an owner-resolution report showing matched users, unmatched owners, and a fallback assignment rule (unassigned records go to the migration admin or a designated Nutshell user). Knock users who are inactive in Knock but exist in Nutshell are flagged to prevent orphaned records.

Knock's Knockbot chatbot configuration and automated follow-up sequences tied to the chatbot have no Nutshell equivalent. These are exported as JSON configuration files in the FlitStack rebuild package. The Nutshell admin or a consultant can use Nutshell Pro's sales automation features (email sequences, task triggers) to approximate parts of the Knockbot logic manually.