CRM migration
Field-level mapping, validation, and rollback between improveit 360 and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
improveit 360
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between improveit 360 and Nutshell.
Complexity
BStandard
Timeline
24–48 hours
Overview
Teams migrate from improveit 360 to Nutshell when they want a simpler CRM with predictable per-user pricing and better usability across their sales team. improveit 360 is a vertically integrated platform for remodelers that bundles CRM, project management, job costing, and quoting — Nutshell is a general-purpose CRM that focuses on people, companies, leads, and pipeline tracking. The migration carries all data improveit 360 stores natively (people, companies, leads, deals, activities, notes, attachments, and custom properties) into Nutshell's corresponding objects. Key challenges include mapping improveit 360's lifecycle stage labels into Nutshell custom fields, collapsing improveit 360's projects and job costing into Nutshell's activity log, and deciding whether to rebuild improveit 360's quoting setup as Nutshell products. We use improveit 360's API export to extract all records, apply field-level mapping, and load into Nutshell via their JSON-RPC API. Workflows, automations, and project-management logic do not migrate — they require manual rebuild 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 improveit 360 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.
improveit 360
Person (Contact)
Nutshell
Person
1:1improveit 360 Person records map directly to Nutshell People using a one-to-one field mapping. All standard contact fields including name, email address, phone number, job title, and physical address transfer as-is with no transformation required. improveit 360 people records that have no linked company association land as standalone Nutshell People records rather than being discarded or incorrectly associated with a placeholder company.
improveit 360
Person (Deal-linked)
Nutshell
Lead
1:1improveit 360 people records that are associated with active or historical deals map to Nutshell Lead records instead of Person records. The company link and all contact details including name, email, phone, and title are preserved during this transformation. This mapping strategy separates pipeline-driven parties from pure contact records, aligning with Nutshell's object model where Leads represent opportunities in the sales pipeline.
improveit 360
Company
Nutshell
Company
1:1improveit 360 Company records map one-to-one to Nutshell Company records without requiring transformation logic. Fields including company name, website URL, industry classification, employee count, annual revenue figures, and complete address information map directly to their Nutshell counterparts. Parent-company relationships transfer as a reference field with circular-dependency checking to prevent infinite loops when parent companies reference each other.
improveit 360
Lead / Prospect
Nutshell
Lead
1:1improveit 360 Lead records map directly to Nutshell Lead records. Lead name, status, monetary value, source, owner, and custom fields transfer as-is. Lead status pick-list values are mapped to Nutshell's lead status options — custom statuses require value-mapping setup during schema configuration.
improveit 360
Deal / Opportunity
Nutshell
Lead
1:1improveit 360 Deals map to Nutshell Lead records. Deal name becomes the Lead name, deal amount maps to the monetary value field, and deal stage maps to Nutshell Lead status via a value-mapping table. improveit 360 deal ID preserved as a custom field for traceability.
improveit 360
Deal Stage / Pipeline
Nutshell
Lead Status + Custom Field
1:1improveit 360 pipeline stages map to Nutshell Lead status values through a value-by-value mapping table defined during schema configuration. Stage-entry timestamps from improveit 360 are preserved by storing them as custom datetime fields on the Nutshell Lead. Stage probability data also transfers as a custom number field on the Lead record, enabling reporting continuity for pipeline forecasts and deal analytics in Nutshell.
improveit 360
Lifecycle Stage (custom property)
Nutshell
Custom Field (Lead)
1:1improveit 360 lifecycle stage labels (Subscriber, Lead, MQL, SQL, Customer, Evangelist) have no native Nutshell equivalent. We create a custom pick-list field (Lifecycle_Stage__c) on Nutshell Leads with the same values so your team can filter and report on prospect progression after migration.
improveit 360
Email Activity
Nutshell
Task
1:1improveit 360 logged email activities transfer as Nutshell Tasks with Type set to 'Email' to distinguish them from other task types. The email subject line becomes the task name, the body content populates the task description field, and the original timestamp and owner assignment are preserved on the task record. The original improveit 360 activity ID is stored as a custom field on the Nutshell Task to support delta-run deduplication and prevent duplicate email records from appearing during subsequent migration runs.
improveit 360
Call / Meeting Activity
Nutshell
Task
1:1improveit 360 call and meeting activities map to Nutshell Tasks with Type set to 'Call' or 'Meeting' respectively. The original start and end timestamps, duration in minutes, subject line, and owner assignment all carry over to the corresponding Nutshell task fields. Activity notes and outcomes recorded in improveit 360 append to the task body field in Nutshell, preserving the full context of each customer interaction.
improveit 360
Note / Attachment
Nutshell
Note / Attachment
1:1improveit 360 notes migrate as Nutshell Notes with the full rich-text content preserved including any formatted text, bullet points, or embedded links. File attachments such as photos, contract documents, proposals, and other files are re-uploaded to Nutshell's attachment store, with the original filename and a reference link preserved on the parent record so users can access the files directly from the Nutshell interface.
improveit 360
Custom Field / Property
Nutshell
Custom Field
1:1improveit 360 custom fields and custom properties are created as Nutshell custom fields under the appropriate object tab (Person, Company, or Lead) based on their source configuration. Multi-value custom fields from improveit 360 map to Nutshell's multi-select pick-list field type, preserving all selected values. Fields that have validation rules defined in improveit 360 are flagged for admin review before migration to ensure data integrity in Nutshell.
improveit 360
Project / Job Costing Record
Nutshell
Task + Custom Fields
1:1improveit 360 project records have no native Nutshell object. We convert project data to Nutshell Tasks with custom fields capturing project stage, budget, and contract value. Your team reviews the converted records and rebuilds the project view in Nutshell's Activities or a project management integration.
| improveit 360 | Nutshell | Compatibility | |
|---|---|---|---|
| Person (Contact) | Person1:1 | Fully supported | |
| Person (Deal-linked) | Lead1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Lead / Prospect | Lead1:1 | Fully supported | |
| Deal / Opportunity | Lead1:1 | Fully supported | |
| Deal Stage / Pipeline | Lead Status + Custom Field1:1 | Fully supported | |
| Lifecycle Stage (custom property) | Custom Field (Lead)1:1 | Fully supported | |
| Email Activity | Task1:1 | Fully supported | |
| Call / Meeting Activity | Task1:1 | Fully supported | |
| Note / Attachment | Note / Attachment1:1 | Fully supported | |
| Custom Field / Property | Custom Field1:1 | Fully supported | |
| Project / Job Costing Record | Task + Custom Fields1: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.
improveit 360 gotchas
No public REST API documented for data export or import
Minimum user requirement of 15 full-time seats
Duplicate prevention rules silently block imported records
Custom reports and dashboards do not transfer via standard export
Pipeline stage names are per-customer configurable
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
Extract full data export from improveit 360 via API
FlitStack AI connects to improveit 360's API using scoped read access and exports all standard objects: people, companies, leads, deals, activities (calls, emails, meetings), notes, attachments, and custom fields. We preserve original create dates, last-modified timestamps, owner assignments, and association links throughout. A pre-extraction schema audit identifies custom field names, pick-list values, and validation rules that require value-mapping setup on the Nutshell side before load.
Configure Nutshell custom fields and lead status mapping
Before loading data, your Nutshell admin (or FlitStack via API) creates the custom fields needed for improveit 360 lifecycle stages, deal metadata, source system IDs, and original create dates. We set up the value-mapping table for lead status and deal stage so Nutshell pick-list values align with improveit 360's labels. Pipeline stage mapping is reviewed against Nutshell's lead status options — any custom improveit 360 stages get added to Nutshell as new status values.
Run sample migration with field-level diff
A representative slice of records — typically 100–500 spanning people, companies, leads, deals, and activities — migrates into Nutshell first. We generate a field-level diff report comparing source values against destination field values so you can verify lifecycle stage mapping, deal-to-lead conversion, owner resolution, and custom field population before the full migration commits. Adjustments to mapping rules are made based on the diff results before proceeding.
Execute full migration with delta-pickup window
Full migration runs in dependency order: Companies first (for foreign-key resolution), then People and Leads, then Deals converted to Leads, then Activities and Notes. A delta-pickup window (typically 24–48 hours after full migration completes) captures any records created or modified in improveit 360 during the cutover period. Owner resolution by email match is applied throughout — unmatched owners are flagged and assigned to a fallback Nutshell user before records land.
Reconcile record counts and verify data completeness
FlitStack AI generates a reconciliation report comparing improveit 360 source counts against Nutshell destination counts for every object. Deal amounts, lead values, and activity timestamps are spot-checked against source values. Any discrepancies are resolved before go-live. Audit logging captures every migration operation, and one-click rollback is available if reconciliation fails — Nutshell is populated with a clean slate and the migration can be re-run with corrected mapping rules.
Platform deep dives
improveit 360
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 improveit 360 and Nutshell.
Object compatibility
2 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
improveit 360: Not publicly documented.
Data volume sensitivity
improveit 360 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 improveit 360 to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your improveit 360 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 improveit 360
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.