CRM migration
Field-level mapping, validation, and rollback between Constructor and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Constructor
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between Constructor and Nutshell.
Complexity
CModerate
Timeline
24–48 hours
Overview
Constructor CRM and Nutshell share a familiar CRM object graph — both organize sales around contacts/people, companies, and deals — but their data models diverge in how leads are handled, how pipelines are scoped, and how custom fields are stored. Nutshell separates People (converted contacts) from Leads (unqualified prospects) and limits pipeline count to the number of seats you purchase, meaning a five-pipeline setup in Constructor requires at least a Pro tier Nutshell plan. FlitStack AI extracts all standard Constructor objects via API and maps them into Nutshell's four primary record types: People, Companies, Leads, and Deals. Custom fields from Constructor are recreated in Nutshell under the respective tabs (Company, Person, or Lead), and each Nutshell custom field must be assigned a type (text, number, date, currency, pick-list) at creation time. Deals from Constructor map into Nutshell Deals, preserving the deal name, amount, stage, close date, and owner. Activity history — calls, emails, meetings, and notes — migrates as Nutshell Activities linked to the parent Person or Deal record. Constructor's automations, workflows, and email templates do not transfer and must be rebuilt in Nutshell using Nutshell's built-in automation tools. Constructor's product catalog, if used, migrates as a Nutshell custom field or product list depending on usage. The migration runs via scoped API access with a delta-pickup window (24–48 hours) capturing in-flight changes before your team goes live in Nutshell.
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 Constructor 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.
Constructor
Contact / Person
Nutshell
Person
1:1Constructor contacts migrate as Nutshell People records. The primary company association links to a Nutshell Company via the Person's company field, preserving the most important business relationship. Constructor contacts without a primary company link land as standalone Nutshell People with no company association, maintaining complete contact information including email, phone, and address details.
Constructor
Contact (unqualified / early stage)
Nutshell
Lead
1:manyConstructor records that have no deal history and a status indicating a new or unqualified prospect can be routed to Nutshell Leads instead of People. FlitStack maps records by evaluating deal count and status fields; your team specifies the routing rule before the migration runs.
Constructor
Company
Nutshell
Company
1:1Constructor companies map directly to Nutshell Companies in a one-to-one relationship. All standard address fields, industry classification, employee count, and annual revenue data transfer directly to corresponding Nutshell fields. Parent–child company hierarchies in Constructor use a parent company ID field that maps to Nutshell's parent company reference, preserving organizational structure during the migration.
Constructor
Deal / Opportunity
Nutshell
Deal
1:1Constructor deals map to Nutshell Deals. Deal name, amount, stage, and close date transfer directly. Nutshell Deal stages must exist before the migration runs — FlitStack generates a stage-mapping plan from Constructor's pipeline stages and your Nutshell plan's configured stages.
Constructor
Pipeline
Nutshell
Pipeline
1:1Constructor pipelines map to Nutshell Pipelines on a one-to-one basis where possible. Nutshell Foundation ships with 1 pipeline; additional pipelines require upgrading to Pro (which supports 5 pipelines) or Business/Enterprise (unlimited pipelines). FlitStack validates your Nutshell plan tier before mapping begins and flags any pipeline count mismatch, ensuring your plan can accommodate the Constructor pipeline structure before data migration starts.
Constructor
Deal Stage
Nutshell
Stage (within Nutshell Pipeline)
1:1Constructor stage names map to Nutshell stage names on a value-by-value basis within each target pipeline, preserving the sales process terminology your team already uses. Stage order, probabilities, and forecast category are reapplied from Nutshell's stage configuration, ensuring accurate sales forecasting. Constructor stage-entered timestamps documenting when each deal moved between stages are preserved in a custom datetime field for historical tracking.
Constructor
Custom Property / Field
Nutshell
Custom Field
1:1Constructor custom properties migrate as Nutshell custom fields, one per Constructor property. Each field must be created in Nutshell under the correct tab (Company, Person, or Lead) with an explicit type before the migration. FlitStack delivers a pre-migration script that creates all custom fields in Nutshell via API.
Constructor
Call / Email / Meeting / Note
Nutshell
Activity
1:1Constructor's logged calls, emails, meetings, and notes migrate as Nutshell Activities. Each activity is linked to its parent Person or Deal record with original timestamp and owner preserved. The activity body text, subject, and direction (inbound/outbound for calls and emails) transfer intact.
Constructor
User / Owner
Nutshell
User
1:1Constructor owner IDs are resolved by email address against Nutshell user accounts. Unmatched owners are flagged before the migration runs; your team either creates a Nutshell account for each or reassigns their records to a fallback owner before data lands.
Constructor
Product / Line Item
Nutshell
Custom Field (Product reference)
1:1Constructor product or line-item data does not have a native Nutshell equivalent. Products referenced in deals migrate as a custom text or pick-list field on the Nutshell Deal. If your team uses Nutshell's paid Quotes & Invoices add-on, product data can be migrated as a product list within that module.
Constructor
Task / To-Do
Nutshell
Task (within Activity)
1:1Constructor tasks linked to contacts or deals migrate as Nutshell Tasks, maintaining their association with the parent record. Completed status, due date, and assigned user information transfer directly to the corresponding Nutshell fields. Standalone tasks without a parent record link to the assignee's Nutshell user record as an open task, ensuring nothing falls through the cracks during the transition.
Constructor
Attachment / File
Nutshell
File (attached to Person / Company / Deal)
1:1Constructor file attachments on people, companies, or deals are re-uploaded to Nutshell and attached to the corresponding record. File size limits from Nutshell's storage configuration apply. Inline images embedded in Constructor notes are extracted and rehosted as Nutshell file attachments.
| Constructor | Nutshell | Compatibility | |
|---|---|---|---|
| Contact / Person | Person1:1 | Fully supported | |
| Contact (unqualified / early stage) | Lead1:many | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Deal / Opportunity | Deal1:1 | Fully supported | |
| Pipeline | Pipeline1:1 | Fully supported | |
| Deal Stage | Stage (within Nutshell Pipeline)1:1 | Fully supported | |
| Custom Property / Field | Custom Field1:1 | Fully supported | |
| Call / Email / Meeting / Note | Activity1:1 | Fully supported | |
| User / Owner | User1:1 | Fully supported | |
| Product / Line Item | Custom Field (Product reference)1:1 | Fully supported | |
| Task / To-Do | Task (within Activity)1:1 | Fully supported | |
| Attachment / File | File (attached to Person / Company / Deal)1:1 | 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.
Constructor gotchas
Reporting and filter limitations make pre-migration data inventory harder
Estimating templates and take-offs carry business logic, not just data
KeyPay payroll data lives in a connected but separate system
Uptime variability requires staged migration windows
Custom integrations (Salesforce, ClickHomes, OCR, ELO) need separate scoping
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
Pre-migration audit and plan setup
FlitStack AI connects to Constructor via scoped API access and inventories all objects: contacts, companies, deals, pipelines, custom properties, activities, and attachments. Simultaneously, we audit your Nutshell account to confirm plan tier, existing pipelines, and custom fields. This audit produces a migration plan document that lists which custom fields need to be created in Nutshell, which Constructor pipelines map to which Nutshell pipelines, and which records have owner email mismatches that need resolution before the migration runs.
Create Nutshell custom fields and validate plan tier
FlitStack generates a custom field creation script that uses Nutshell's API to create all necessary custom fields under the Company, Person, and Lead tabs with the correct field types and pick-list values. If your Constructor setup uses more pipelines than your Nutshell plan allows, this step surfaces the plan mismatch so your team can upgrade before data mapping begins. No data is migrated in this step — the schema is validated first.
Resolve owners and map pipeline stages
Constructor owner records are matched against Nutshell users by email address. Records belonging to unmatched owners are flagged with a pre-migration report. Your team either invites the missing users to Nutshell or assigns those records to a fallback owner. Simultaneously, Constructor deal stage names are mapped to Nutshell stage names within each pipeline, and stage probabilities are aligned to Nutshell's stage configuration. Any stage names with no Nutshell equivalent are flagged for manual mapping before the full migration runs.
Sample migration with field-level diff
A representative slice — typically 100–300 records spanning contacts, companies, deals, and activities — migrates into Nutshell first. FlitStack generates a field-level diff report showing source values against destination values for every mapped field. You verify that custom field values landed correctly, stage names mapped as expected, and activity history is linked to the correct parent records. You approve or request adjustments before the full migration proceeds.
Full migration with delta-pickup and rollback
The full dataset migrates in dependency order: Companies first, then People and Leads, then Deals, then Activities, then Tasks, then Attachments. A delta-pickup window (24–48 hours) runs after the bulk migration to capture any Constructor records modified during the cutover window. All operations are logged in an audit trail. If reconciliation fails — record counts do not match, required fields are blank, or owner resolution produced unexpected results — one-click rollback reverts the Nutshell environment to its pre-migration state while your team addresses the root cause.
Platform deep dives
Constructor
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 4 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Constructor and Nutshell.
Object compatibility
4 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
Constructor: Not publicly documented — no published rate limits. Typical SaaS limits assumed and confirmed during scoping..
Data volume sensitivity
Constructor 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 Constructor to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Constructor 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 Constructor
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.