CRM migration

Migrate from Levitate to Nutshell

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

Levitate logo

Levitate

Source

Nutshell

Destination

Nutshell logo

Compatibility

75%

6 of 8

objects map 1:1 between Levitate and Nutshell.

Complexity

BStandard

Timeline

2-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Levitate logo

Levitate

What's pushing teams away

  • The single $349/month flat rate has no free tier and no lower-cost entry point, pushing price-sensitive solo agents and micro-SMBs toward HubSpot, Brevo, or Constant Contact which start at $9–$15/month.
  • Levitate lacks a published API and robust export tooling — contacts can be exported via UI, but there is no documented bulk API for automations, custom fields, or engagement history, making self-serve migrations difficult.
  • Businesses scaling beyond 20–30 users often outgrow the flat-rate model and move to per-seat CRMs like HubSpot that offer more granular user management, role-based permissions, and advanced pipeline tooling.
  • Some users report that the platform's focus on email-first outreach feels limiting when they need full-featured pipeline management, task tracking, or quoting — features they find in platforms like HubSpot or Salesforce Marketing Cloud.

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 Levitate objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

Levitate 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

maps to

Nutshell

Custom Field (Multi-Select Picklist)

lossy
Fully supported

Levitate 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

maps to

Nutshell

Company

1:1
Fully supported

Levitate 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

maps to

Nutshell

Campaign

1:1
Fully supported

Levitate 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

maps to

Nutshell

Workflow (rebuild required)

lossy
Fully supported

Levitate 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

maps to

Nutshell

User

1:1
Fully supported

Levitate 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

maps to

Nutshell

Activity

1:1
Fully supported

Levitate 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

maps to

Nutshell

Custom Date Field

1:1
Fully supported

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

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.

Levitate logo

Levitate gotchas

High

No public API — automation logic is not exportable

Medium

Key Dates are Levitate-specific custom fields

Low

Split billing requires manual credit card management

Low

Flat-rate billing continues until cancelled

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

  • Levitate automations cannot be exported as workflow logic

    Levitate stores automations as server-side workflow definitions with no export capability. The only extractable artifact is which contacts are currently enrolled in which sequence. We handle this by extracting the enrollment state and preserving tag assignments, then delivering a written automation inventory that documents every active sequence with its trigger, conditions, delay steps, email actions, and tag actions. The customer's admin rebuilds these in Nutshell's automation builder. Automations that are not rebuilt will not fire post-migration, which can interrupt client outreach cadences built in Levitate.

  • Contact notes are not in the self-serve export

    Levitate's UI-based contact CSV export does not include profile notes. We request contact notes directly from Levitate Support as part of the discovery process, but note that response times vary. If notes cannot be obtained before migration, they are flagged as a manual data-entry item post-migration. We do not delay the migration for missing notes unless the customer explicitly requests note extraction as a blocker.

  • Key Date fields must be pre-created in Nutshell

    Levitate Key Dates are a distinct field type that must map to custom date fields in Nutshell. If the customer has not pre-created these fields in Nutshell before migration, Key Date values land as plain text and automation triggers cannot be rebuilt. We scan for Key Date fields during discovery, confirm the Nutshell schema has matching custom date fields, and flag any mismatch before the import phase begins.

  • Levitate flat-rate billing runs through the paid period

    Levitate charges automatically on the billing anniversary date and has no prorated cancellation. The subscription continues through the paid period. We align the migration cutover window to occur just after a billing cycle starts so the customer pays for one final clean period, then cancels. We also flag the cancellation path (Account Settings > Admin > Users & Billing) which requires an Administrator role. Any pending split billing installments should be resolved before initiating account closure.

Migration approach

Six steps for a successful Levitate to Nutshell data migration

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

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

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

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

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

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

Context on both ends of the pair

Levitate logo

Levitate

Source

Strengths

  • Flat-rate pricing includes unlimited contacts, tags, and automations with no per-seat or per-contact overage charges.
  • Emails route through the user's own Gmail or Outlook server, achieving 60%+ open rates versus 20% for mass blast tools.
  • Customer support ratings consistently exceed 4.9/5 across G2, Capterra, and GetApp verified reviews.
  • Built-in AI assistant generates and translates content across 10 languages without leaving the platform.
  • Strong vertical integrations with insurance (Vertafore, AMS360) and legal (Clio) practice management systems.

Weaknesses

  • Single flat-rate tier at $349/month has no free tier, trial, or lower-cost entry point for solo users.
  • No publicly documented API or bulk data export endpoint — contact export is UI-only, automation export is not available.
  • Automations cannot be exported as portable logic; only enrollment state is extractable, requiring workflow re-build at destination.
  • Social media posts, handwritten card orders, and SMS consent records are not independently exportable.
  • Limited customization of pipeline stages, deal objects, or deal-specific fields — the platform is contact-centric rather than opportunity-centric.
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?

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

B

Overall complexity

Standard migration

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

  • Object compatibility

    B

    1 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

    Levitate: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Levitate 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 Levitate to Nutshell data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Levitate to Nutshell migrations complete in two to three weeks for accounts under 10,000 contacts with no complex tag taxonomy. Migrations with large tag taxonomies (hundreds of distinct tags), multiple active campaigns with engagement history, or extensive Key Date field sets move to four to six weeks because of the manual schema preparation required in Nutshell and the automation inventory documentation work.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Levitate.
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