CRM migration
Field-level mapping, validation, and rollback between Cloze and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Cloze
Source
Nutshell
Destination
Compatibility
7 of 9
objects map 1:1 between Cloze and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Cloze to Nutshell is a platform simplification for teams that find Cloze's real estate bias and beta-only API constraining at scale. Cloze uses People, Companies, Projects (aliased as Deals or Properties), Segments, and a Timeline activity log as its core objects; Nutshell uses Contacts, Companies, Deals, and Activities with a simpler stage model. We handle the object-level mapping, resolve owner lookups by email, preserve tag memberships as custom multi-select fields, and migrate activity metadata through Nutshell's REST API with rate-limit handling. We do not migrate Cloze Campaigns, Workflows, or the Cloze Score metric as these have no direct Nutshell equivalent — we deliver a written inventory of these for the customer's admin to evaluate post-migration.
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 Cloze 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.
Cloze
People
Nutshell
Contact
1:1Cloze People records map directly to Nutshell Contacts. Standard fields (first_name, last_name, email, phone, address, social URLs) map to Nutshell's Contact fields. Custom fields on People transfer to Nutshell custom Contact fields. The Cloze Stage property (Lead, Potential, Active, Inactive, Past, Lost) maps to a combination of Nutshell's Contact Status field and a custom lifecycle_stage__c field for audit clarity.
Cloze
Company
Nutshell
Company
1:1Cloze Company records map to Nutshell Company records with a direct field-to-field translation. Address, social links, industry, and website fields align to Nutshell's standard Company fields. Company-level custom fields migrate as Nutshell custom Company fields. The People-to-Company link in Cloze becomes the Nutshell Contact-to-Company relationship established during Contact import.
Cloze
Projects (Deals/Properties)
Nutshell
Deal
1:1Cloze Projects (aliased as Deals or Properties depending on the customer's naming config) map to Nutshell Deals. The Cloze Stage field (Potential, Active, Done, Lost) maps to Nutshell's pipeline stage values, which we configure to match the customer's existing stage labels during migration. Custom fields on Projects transfer to Nutshell custom Deal fields. Real estate-specific stage labels (e.g., Under Contract, Listed) are normalized to the destination stage model.
Cloze
Segment
Nutshell
Custom Field (multi-select picklist)
lossyCloze Segments and Audience memberships are preserved by mapping each contact's segment assignment to a custom multi-select picklist field in Nutshell (e.g., segment__c). Segments like Customers, Leads, Prospects, Inactive map to the corresponding values in the custom field. Multiple segment memberships on a single contact result in comma-separated values in the Nutshell multi-select field.
Cloze
Tag
Nutshell
Custom Field (multi-select) or Note
lossyCloze tags on People and Companies are preserved as a custom multi-select picklist tag__c field in Nutshell. Teams with over 100 unique tags may prefer a tag-strategy decision during scoping: either a multi-select field (cleaner UI, easier filtering) or a Note record per contact listing all original tags (preserves full tag history without field length constraints). The customer chooses the strategy during discovery.
Cloze
Custom Fields
Nutshell
Custom Fields
1:1Cloze custom fields on People, Companies, and Projects (text, number, date, choice field types) map to Nutshell custom fields of the equivalent type. Choice fields map to Nutshell picklist fields. We flag any deprecated or deleted custom fields in Cloze that may contain stale data and exclude them from migration to prevent clean data from being contaminated by orphaned field definitions.
Cloze
Timeline Entries
Nutshell
Activity (Call, Email, Meeting, Task)
1:1Cloze Timeline records (emails, calls, texts, meetings, notes) migrate as Nutshell Activities. Call logs map to Nutshell Task with Call type; meeting records map to Nutshell Task with Meeting type; email metadata maps to Nutshell Email records linked to the Contact. Note content migrates to Nutshell Note records linked to the parent Contact, Company, or Deal. We preserve the original timestamp from Cloze as the Activity date. Raw email body content may be truncated depending on what Cloze retained; we flag this as a data completeness caveat during discovery.
Cloze
Owner
Nutshell
User
1:1Cloze Owners map to Nutshell Users by email address match. We extract all distinct owner references from People, Company, and Project records and match against the destination Nutshell account's User table. Any Cloze Owner without a matching Nutshell User enters a reconciliation queue for the customer's admin to provision the corresponding user account before the final migration run.
Cloze
Campaigns
Nutshell
Custom Object (documentation only)
1:1Cloze Campaigns (available only on Cloze Business Platinum) are migrated as a written record inventory, not as an active campaign engine in Nutshell. Nutshell does not include a native campaign feature, so we preserve campaign definitions (name, audience criteria, stage triggers) as a custom Report in the destination for the customer's admin to evaluate against Nutshell-compatible alternatives (e.g., email marketing platform integrations).
| Cloze | Nutshell | Compatibility | |
|---|---|---|---|
| People | Contact1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Projects (Deals/Properties) | Deal1:1 | Fully supported | |
| Segment | Custom Field (multi-select picklist)lossy | Fully supported | |
| Tag | Custom Field (multi-select) or Notelossy | Fully supported | |
| Custom Fields | Custom Fields1:1 | Mapping required | |
| Timeline Entries | Activity (Call, Email, Meeting, Task)1:1 | Mapping required | |
| Owner | User1:1 | Fully supported | |
| Campaigns | Custom Object (documentation only)1:1 | Mapping required |
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.
Cloze gotchas
Cloze API requires manual beta access approval
Export requires Manager or Admin role permissions
Campaigns feature gated behind Business Platinum
Real estate terminology bleeds into core objects
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 export credentialing
We audit the Cloze account for record counts across People, Companies, Projects/Deals, Segments, Tags, and Timeline volume. We verify the exporting user's role (Manager or Admin required for team-wide exports) and initiate the Cloze API beta access request via email to Cloze support. If API access is not granted within the scoping window, we prepare a CSV/Excel export workflow using the Cloze UI export tool under Settings > Import/Export. We deliver a discovery summary including record counts, custom field inventory, and stage label mapping for the customer's review.
Nutshell account setup and schema design
We verify the customer's Nutshell account and edition tier. We design the destination schema: custom fields on Contact, Company, and Deal objects (mapped from Cloze custom properties), pipeline stage values (normalized from Cloze's stage labels), and any multi-select fields for Segment and Tag preservation. Nutshell's API uses bearer token authentication; we coordinate with the customer to generate an API key from Nutshell Settings > API Access if one does not already exist.
Sandbox validation and mapping sign-off
We run a test migration into a Nutshell Sandbox or a temporary destination org using a subset of production data (typically 10-15% of records). The customer's admin reviews the migrated Contact, Company, and Deal records against the Cloze source for field accuracy, stage label correctness, and tag membership preservation. We correct any mapping errors before the production migration run. This step also validates that Nutshell's field-length limits and picklist constraints do not truncate any incoming data.
Owner and User reconciliation
We extract every distinct Owner referenced in Cloze (on People, Companies, and Projects/Deals) and match by email address against the destination Nutshell account's User list. Any unmatched Owners enter a reconciliation queue. The customer's Nutshell admin provisions any missing user accounts before the production migration begins. OwnerId references on records must be resolvable at insert time, so this step blocks the main migration run if unresolved users remain.
Production migration in dependency order
We run production migration in record-dependency order: Companies first (Hub for Account/Company lookup), then Contacts (with CompanyId resolved), then Deals (with OwnerId and related Contact/Company resolved), then custom fields and Tags/Segments as multi-select fields on the respective records. Activity metadata (calls, emails, meetings, tasks) migrates through Nutshell's REST API with rate-limit handling and exponential backoff. We emit a row-count reconciliation report after each phase before the next phase begins.
Cutover, validation, and admin handoff
We freeze Cloze write access during the cutover window, run a final delta migration of any records modified since the initial extraction, then hand the Nutshell account to the customer's admin as the system of record. We deliver the written Campaign inventory document and the Workflow/Automation rebuild list for the customer's admin to evaluate against Nutshell-compatible tools. We support a three-day post-migration hypercare window for reconciliation issues.
Platform deep dives
Cloze
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 Cloze 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
Cloze: Not publicly documented.
Data volume sensitivity
Cloze 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 Cloze to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Cloze 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 Cloze
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.