CRM migration
Field-level mapping, validation, and rollback between Knack and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Knack
Source
Nutshell
Destination
Compatibility
7 of 9
objects map 1:1 between Knack and Nutshell.
Complexity
BStandard
Timeline
1-3 weeks
Overview
Knack organizes data into custom-built Tables with Connection fields for relationships, while Nutshell uses a standard CRM object model (People, Companies, Leads, Opportunities). These fundamentally different schemas require a structural translation at migration time rather than a direct field copy. We begin by auditing every Knack Table and Connection, then map each Table to the nearest Nutshell object (People, Companies, Leads, Opportunities) or to a custom field where no native object fits. Connection fields become Nutshell relationship lookups or multi-select fields depending on cardinality. File attachments are downloaded from Knack's signed-URL storage and re-uploaded to Nutshell. Knack's Workflow rules, automation rules, and Scheduled Tasks do not migrate; we document them for the customer's admin to rebuild. Nutshell's JSON-RPC API accepts add and edit requests without rate limiting on inbound writes, though large find() queries are throttled. The migration runs in discovery, sandbox validation, and production phases, with record counts reconciled at each gate.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Knack object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Knack
Table (Contacts, Customers, or People)
Nutshell
Person
1:1Knack Tables storing individual contact records map to Nutshell Person. Standard text fields (name, email, phone) map to Nutshell's built-in Person fields (name, emails, phones). Custom fields (industry, job title, source) map to Nutshell custom Person fields. We resolve the Knack Table name during discovery to determine whether the table holds contacts or companies before mapping.
Knack
Table (Organizations, Accounts, or Companies)
Nutshell
Company
1:1Knack Tables storing organizational records map to Nutshell Company. Company name, address, website, and industry fields map to Nutshell Company fields. If the Knack Table has no organizational records, this mapping is skipped. We use the Company name as the dedupe key during import to avoid duplicate Accounts.
Knack
Table (Leads or Prospects)
Nutshell
Lead
1:1Knack Tables tagged during discovery as holding unqualified prospects map to Nutshell Lead. Status fields from Knack (new, contacted, qualified, unqualified) map to Nutshell's Lead status values. If the Knack Table is named 'Leads' or contains a status field with the values above, we treat it as a Lead table rather than a Person table.
Knack
Table (Deals, Projects, or Opportunities)
Nutshell
Opportunity
1:1Knack Tables holding deal or project records map to Nutshell Opportunity. Deal value, stage, close date, and owner fields map to Nutshell Opportunity fields. Pipeline stages from Knack become Nutshell pipeline stages, which we configure before import. Owner assignment resolves by email against the Nutshell User table.
Knack
Connection Field (one-to-many)
Nutshell
Linked Record or Lookup field
1:1Knack Connection fields linking one Table to another (such as a Deal linked to a Person or Company) become Nutshell Linked Records. We resolve the target record by matching on the dedupe key (email for Person, name for Company) at migration time. Many-to-many Connection fields become multi-select linked record fields in Nutshell.
Knack
File field
Nutshell
File attachment on Person, Company, or Opportunity
1:1Knack file fields storing documents, images, and PDFs are downloaded from Knack's signed-URL storage and re-uploaded to the corresponding Nutshell record as a file attachment. We preserve the original filename and link the attachment to the parent record (Person, Company, or Opportunity) at the correct API endpoint. Files larger than Nutshell's attachment size limit are flagged for the customer.
Knack
Record History (Pro and Corporate)
Nutshell
Audit Log or Activity
1:1Knack Record History (available 1 month on Pro, 2 months on Corporate, 3 months on Enterprise) is exported as Activity records on the target Nutshell object with a descriptive note field capturing the field change and timestamp. History beyond the available plan tier is not available for export from Knack. We flag the history window size during discovery.
Knack
View (filtered record subsets)
Nutshell
Saved View in Nutshell
lossyKnack Views are saved filtered or sorted subsets of a Table. We document each View's filter conditions and field order during discovery, then replicate the logic as a Nutshell saved view on the target object. Views that apply to Tables with no direct Nutshell equivalent are flagged for manual rebuild in Nutshell's filter builder.
Knack
User Role and Permission
Nutshell
Team or User assignment
lossyKnack roles control page and record access. We export role names and permission scopes as metadata. Nutshell uses Teams and individual User assignments; we map Knack role names to Nutshell Teams or individual User records and document the permission mapping for the customer's admin to finalize in Nutshell's settings.
| Knack | Nutshell | Compatibility | |
|---|---|---|---|
| Table (Contacts, Customers, or People) | Person1:1 | Fully supported | |
| Table (Organizations, Accounts, or Companies) | Company1:1 | Fully supported | |
| Table (Leads or Prospects) | Lead1:1 | Fully supported | |
| Table (Deals, Projects, or Opportunities) | Opportunity1:1 | Fully supported | |
| Connection Field (one-to-many) | Linked Record or Lookup field1:1 | Fully supported | |
| File field | File attachment on Person, Company, or Opportunity1:1 | Fully supported | |
| Record History (Pro and Corporate) | Audit Log or Activity1:1 | Fully supported | |
| View (filtered record subsets) | Saved View in Nutshelllossy | Fully supported | |
| User Role and Permission | Team or User assignmentlossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Knack gotchas
No native backup or export feature in Knack
Classic to Next-Gen platform migration is not automatic
Record limits count every row across all Tables
API rate limits are not publicly documented with specific numbers
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Discovery and Knack schema audit
We audit every Knack Table, field type, Connection field, file field, and View. We determine the entity type for each Table (person, organization, deal, hybrid, or metadata), map Connection fields to understand foreign-key dependencies, and count total records and file attachment volume. We also document active Workflows, Scheduled Tasks, and User Roles. This output is a written schema inventory that drives the object mapping plan.
Nutshell schema preparation
We configure the Nutshell destination org before any data moves: custom fields on Person, Company, Lead, and Opportunity objects are created to match Knack fields that have no native Nutshell equivalent. Pipeline stages and statuses are configured to match the Knack deal stages. Teams are created to map Knack User Roles. The destination schema is validated in a Nutshell test environment before production migration begins.
Sandbox migration and reconciliation
We run a full migration into a Nutshell sandbox or staging environment using the full record volume. The customer's admin reconciles record counts (People in, Companies in, Opportunities in), spot-checks 20-30 records against the Knack source, and validates that Connection fields resolved correctly. Any schema corrections, mapping adjustments, or dedupe key collisions are resolved here before production migration.
File attachment extraction and staging
We download all files from Knack file fields in parallel batches, preserving the original filename and content type. Files are staged in our migration storage with a manifest linking each file to its parent Knack record ID. If any file exceeds Nutshell's attachment size limits, we flag it for the customer's admin to store externally and link.
Production migration in dependency order
We run production migration in record-dependency order: Companies first (if present), then People and Leads, then Opportunities (resolving all Connection field lookups by dedupe key), then file attachments. Activities and Record History follow. Each phase emits a row-count reconciliation report before the next phase begins. Connection fields that could not resolve are logged to the reconciliation queue for the customer's admin to resolve manually.
Cutover, validation, and Workflow handoff
We freeze Knack writes during cutover, run a final delta migration of records modified during the migration window, then enable Nutshell as the system of record. We deliver the Workflow and Scheduled Task inventory document to the customer's admin team with recommended Nutshell equivalents. We support a three-day hypercare window for reconciliation issues. Post-migration admin configuration, team setup, and automation rebuild are outside standard migration scope.
Platform deep dives
Knack
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Knack and Nutshell.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Knack: Not publicly documented with specific numbers; 429 responses observed under heavy load.
Data volume sensitivity
Knack doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Knack to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Knack to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Knack
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.