CRM migration
Field-level mapping, validation, and rollback between Levitate and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Levitate
Source
Nutshell
Destination
Compatibility
6 of 8
objects map 1:1 between Levitate and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Levitate organizes its data around Contacts with Tags driving segmentation and automation enrollment, while Nutshell uses a conventional deal-pipeline model with Accounts, People, Leads, and Opportunities. These structural differences require deliberate mapping: Levitate Tags become custom multi-select picklist fields in Nutshell, Levitate Key Dates become custom date fields, and Levitate Campaigns with aggregate engagement stats migrate to Nutshell Campaigns. The most significant gap is automation logic — Levitate stores server-side workflow definitions that cannot be exported as portable JSON, so every active sequence requires manual reconstruction in Nutshell's automation builder. We extract contacts via Levitate's UI export, resolve tag assignments and engagement summaries, then load into Nutshell via the REST API with proper field typing.
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 Levitate 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.
Levitate
Contact
Nutshell
Person
1:1Levitate Contacts map to Nutshell People. Standard fields (name, email, phone, company, address) map directly. Levitate profile notes are requested from Levitate Support directly since they are not available in the self-serve CSV export. We preserve the original Levitate contact ID in a custom field levitate_id__c for reconciliation. Key Date values (birthday, renewal date) land in Nutshell custom date fields that the customer must pre-create during schema preparation.
Levitate
Tag
Nutshell
Custom Field (Multi-Select Picklist)
lossyLevitate Tags are the primary segmentation mechanism and drive automation triggers. We preserve the full tag taxonomy as a Nutshell multi-select picklist custom field on the Person object. Each contact's tag assignments map to the picklist values during import. If tag taxonomy exceeds the picklist size limits, we split tags across multiple custom fields or use Nutshell's tagging feature if applicable to the destination tier.
Levitate
Company
Nutshell
Company
1:1Levitate contacts optionally link to a company name; if present, we create a corresponding Nutshell Company record and resolve the lookup on the Person record during import. Levitate does not have a separate Account object, so companies are often stored as free-text on the contact record — we promote distinct company names into Nutshell Companies and link all contacts sharing that name.
Levitate
Campaign
Nutshell
Campaign
1:1Levitate Campaigns with aggregate engagement stats (open rate, click rate, send volume) migrate to Nutshell Campaigns. Individual email performance data is captured as aggregate Campaign statistics rather than per-contact engagement records. Last engagement date and overall engagement score migrate as custom fields on the Nutshell Campaign record.
Levitate
Automation
Nutshell
Workflow (rebuild required)
lossyLevitate automations are server-side workflow sequences with email steps, delays, conditional branches, and tag actions. The automation logic itself is not exportable — only enrollment state (which contacts are currently in which sequence) is extractable. We deliver a written inventory of every active Levitate automation documenting its trigger, conditions, delay rules, and action sequence. The customer's admin rebuilds these in Nutshell's automation builder; we provide the inventory as the rebuild reference document.
Levitate
User
Nutshell
User
1:1Levitate user accounts (owner, admin, member roles) are listed and matched to Nutshell Users by email address during migration. Role definitions and permission scopes are not fully exportable from Levitate. We flag the owner and active user list and document the Nutshell permission model equivalents so the customer's admin can configure roles post-migration.
Levitate
Engagement: Email / Call / Meeting / Note
Nutshell
Activity
1:1Levitate engagement events (opens, clicks, replies, calls, meetings, notes) are captured as aggregate last-engagement dates and engagement counts on the contact record rather than as independent activity log entries. We migrate available engagement history as Activity notes attached to the Nutshell Person record with the timestamp preserved. SMS logs migrate as Activity entries with message direction and content.
Levitate
Key Date
Nutshell
Custom Date Field
1:1Levitate Key Dates (birthday, renewal date, policy expiration, custom age milestones) are a Levitate-specific field type that drives date-triggered automations. We flag each Key Date field during discovery and confirm that the customer has created equivalent custom date fields in Nutshell before import. Key Dates land as typed date fields in Nutshell but will not trigger automations unless the customer rebuilds those triggers in Nutshell's automation builder.
| Levitate | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Tag | Custom Field (Multi-Select Picklist)lossy | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Campaign | Campaign1:1 | Fully supported | |
| Automation | Workflow (rebuild required)lossy | Fully supported | |
| User | User1:1 | Fully supported | |
| Engagement: Email / Call / Meeting / Note | Activity1:1 | Fully supported | |
| Key Date | Custom Date Field1: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.
Levitate gotchas
No public API — automation logic is not exportable
Key Dates are Levitate-specific custom fields
Split billing requires manual credit card management
Flat-rate billing continues until cancelled
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 data audit
We audit the Levitate account via the UI export for contacts, tag taxonomy, campaign history, and automation enrollment state. We extract user list and owner assignments from Levitate Support. We document the Key Date fields in use, the tag taxonomy size, and the campaign engagement summary data. The discovery output is a written scope with record counts, tag taxonomy, automation inventory, and a Nutshell schema checklist for the customer to complete before import begins.
Nutshell schema preparation
The customer pre-creates custom fields in Nutshell: custom date fields for each Levitate Key Date, a multi-select picklist for tag taxonomy, and any custom fields mapped from Levitate contact properties. We provide a schema checklist with field names and types. Nutshell supports custom fields for People, Companies, and Leads from the Settings > Data > Custom Fields menu. We validate the schema is in place before any import begins to avoid field mapping failures.
Tag taxonomy mapping and Key Date field resolution
We map each Levitate Tag to a Nutshell multi-select picklist value. If the tag taxonomy exceeds picklist size limits, we split across multiple fields or recommend a tagging strategy. For Key Dates, we match each Levitate Key Date field to its pre-created Nutshell custom date field by name and ensure the date format is consistent (ISO 8601 preferred). Any Key Date without a matching Nutshell field is flagged and held from import until resolved.
Import in dependency order
We load data into Nutshell in dependency order: Companies first (from Levitate company names), then People with Company lookups resolved, then tag assignments via the multi-select picklist, then custom date fields for Key Dates, then campaign engagement summaries. We use Nutshell's REST API with batch chunking and rate-limit handling to insert records. Each phase emits a row-count reconciliation report.
Automation inventory delivery and rebuild handoff
We deliver the automation inventory document listing every active Levitate automation with its trigger conditions, delay rules, email content reference, tag actions, and sequence order. This document serves as the rebuild brief for the customer's admin in Nutshell's automation builder. We do not rebuild automations as Nutshell workflow logic inside the migration scope. Social media posts, handwritten card orders, and SMS consent records are not migratable and are documented as exclusions in the scope agreement.
Cutover, validation, and go-live
We freeze writes in Levitate during the final cutover window, run a delta import of any records modified during migration, then enable Nutshell as the system of record. We deliver a final reconciliation report comparing Levitate source counts against Nutshell destination counts for each object. We support a three-day hypercare window to resolve any data quality issues surfaced by the customer's team. Account cancellation in Levitate is the customer's action from Account Settings > Admin > Users & Billing.
Platform deep dives
Levitate
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 Levitate 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
Levitate: Not publicly documented.
Data volume sensitivity
Levitate 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 Levitate to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Levitate 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 Levitate
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.