CRM migration

Migrate from Constructor to Nutshell

Field-level mapping, validation, and rollback between Constructor and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Constructor logo

Constructor

Source

Nutshell

Destination

Nutshell logo

Compatibility

92%

11 of 12

objects map 1:1 between Constructor and Nutshell.

Complexity

CModerate

Timeline

24–48 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Constructor logo

Constructor

What's pushing teams away

  • G2 reviewers report uptime falling below 90% during some periods, which is below the threshold most modern SaaS customers tolerate.
  • Reporting is consistently called out as weak — reviewers note reports are not always available and filters are 'tough to administer and utilize'.
  • Filter management is described as difficult to manage and use effectively, slowing down ad-hoc data analysis and list-building.
  • Customers seeking strong native integrations beyond the listed Salesforce / ClickHomes / OCR / ELO connectors hit gaps and have to commission custom API work.
  • Builders that expand outside ANZ outgrow the platform's regional focus, since progress-claim conventions and tax treatments are tuned for Australian and New Zealand construction practice.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Constructor objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

Constructor 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)

maps to

Nutshell

Lead

1:many
Fully supported

Constructor 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

maps to

Nutshell

Company

1:1
Fully supported

Constructor 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

maps to

Nutshell

Deal

1:1
Fully supported

Constructor 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

maps to

Nutshell

Pipeline

1:1
Fully supported

Constructor 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

maps to

Nutshell

Stage (within Nutshell Pipeline)

1:1
Fully supported

Constructor 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

maps to

Nutshell

Custom Field

1:1
Fully supported

Constructor 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

maps to

Nutshell

Activity

1:1
Fully supported

Constructor'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

maps to

Nutshell

User

1:1
Fully supported

Constructor 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

maps to

Nutshell

Custom Field (Product reference)

1:1
Fully supported

Constructor 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

maps to

Nutshell

Task (within Activity)

1:1
Fully supported

Constructor 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

maps to

Nutshell

File (attached to Person / Company / Deal)

1:1
Fully supported

Constructor 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.

Gotchas + challenges

What specifically takes care here

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 logo

Constructor gotchas

High

Reporting and filter limitations make pre-migration data inventory harder

High

Estimating templates and take-offs carry business logic, not just data

Medium

KeyPay payroll data lives in a connected but separate system

Medium

Uptime variability requires staged migration windows

Low

Custom integrations (Salesforce, ClickHomes, OCR, ELO) need separate scoping

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Constructor's many-to-many contact–company associations collapse to a single primary company in Nutshell

    Constructor permits a contact to be associated with multiple companies simultaneously. Nutshell Person records hold one primary Company reference. When a Constructor contact has multiple associated companies, FlitStack migrates the most-recently-modified company as the primary Nutshell Company and surfaces the remaining associations as Person notes or a custom multivalue field. Your team decides whether to document secondary companies in a note or accept the primary-only association. This is a structural limitation of Nutshell's data model — not a FlitStack mapping error.

  • Constructor pipelines exceeding Nutshell plan limits require plan upgrade before migration

    Nutshell Foundation ships with one pipeline; Nutshell Pro supports five pipelines; Business and Enterprise tiers allow unlimited pipelines. If your Constructor setup uses more pipelines than your current Nutshell plan allows, the migration plan will flag the excess and require a plan upgrade. Pipeline-to-pipeline mapping is blocked until the plan is upgraded, because Nutshell does not allow creating additional pipelines on a plan that does not include them. FlitStack validates the plan tier during the pre-migration audit and surfaces any mismatch before data mapping begins.

  • Constructor's lifecycle or custom status fields need a custom field in Nutshell before migration

    Constructor tracks prospect lifecycle or contact status using a custom property that has no native equivalent in Nutshell. Nutshell does not have a lifecycle stage field on People or Leads — it uses a simple Lead/Person split. FlitStack migrates any Constructor status or lifecycle property as a custom pick-list field on the Nutshell Person or Lead record. The field must be created in Nutshell under the appropriate tab (Person or Lead) with matching pick-list values before the migration runs. FlitStack generates a custom field creation script during the pre-migration planning phase.

  • Constructor automations and workflows do not migrate — they must be rebuilt in Nutshell

    Constructor workflows, automation rules, assignment rules, and sequence enrollment data are not stored as records that export cleanly. They are platform-state configurations that cannot be translated to Nutshell's automation model. FlitStack migrates data only. Your team should export Constructor's automation definitions as a reference document before the migration cutover, then rebuild those automations in Nutshell using Nutshell's built-in automation tools (available on Pro and Business plans). FlitStack does not transfer any workflow, automation, or sequence logic.

  • Constructor product catalog has no native Nutshell equivalent and may require an add-on

    Constructor's product or line-item data associated with deals has no direct Nutshell standard object. Nutshell's Deals object does not natively support line items with quantity and unit price. If your team uses deal products in Constructor, FlitStack migrates the product reference as a custom text field or pick-list on the Nutshell Deal. If you need full quote management with line items, you must purchase Nutshell's Quotes & Invoices add-on (available on Business plan) and migrate product data as a product list within that module.

Migration approach

Six steps for a successful Constructor to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Constructor logo

Constructor

Source

Strengths

  • Tightly integrated Sales, Estimating, Accounting, Scheduling, and Payroll modules under one platform.
  • Visual take-off tools and template-driven estimating tailored to residential building workflows.
  • KeyPay-powered payroll with STP Phase 2 compliance for Australian statutory reporting.
  • Cost-plus and progress-claim billing native to the platform — no separate accounting bolt-on needed.
  • Australian-owned with development team in Australia, tuned to ANZ residential-building practice.

Weaknesses

  • Reporting and filter UX is widely cited as weak by G2 reviewers.
  • Uptime has been reported under 90% during some periods.
  • Limited native integration catalog — most connections (Salesforce, ClickHomes, OCR, ELO) require custom build.
  • Regional focus on ANZ residential construction limits fit for builders outside that geography.
  • Public API documentation is thin; integration partners typically engage the vendor for credentials and specs.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Moderate CRM migration. 4 of 8 objects need a mapping; the rest are 1:1.

C

Overall complexity

Moderate migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Constructor and Nutshell.

  • Object compatibility

    C

    4 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Constructor: Not publicly documented — no published rate limits. Typical SaaS limits assumed and confirmed during scoping..

  • Data volume sensitivity

    B

    Constructor doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Constructor to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Constructor to Nutshell data migrations

Answers to the questions buyers ask most during Constructor to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Constructor to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Constructor-to-Nutshell migrations complete in 24–48 hours of clock time for under 25,000 records. Setup and custom field creation add 1–2 days of planning before data moves. Larger databases with 250k+ records or multi-pipeline setups extend to 4–7 days. The longest single step is typically validating the Nutshell plan tier against the number of Constructor pipelines being migrated, because upgrading the Nutshell plan may be required before field mapping can begin.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Constructor.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day