CRM migration
Field-level mapping, validation, and rollback between iPresso and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
iPresso
Source
Nutshell
Destination
Compatibility
5 of 8
objects map 1:1 between iPresso and Nutshell.
Complexity
CModerate
Timeline
3-5 weeks
Overview
Moving from iPresso to Nutshell is a migration from a multi-channel marketing automation platform to a focused sales CRM. iPresso consolidates Email, SMS, Web Push, and Print channels against contact profiles with behavioral event tracking; Nutshell provides pipeline management, contact organization, and integrated sales engagement starting at $16 per user per month with unlimited contacts on all paid plans. The primary migration challenge is that iPresso does not publish a public API, which means data extraction requires direct coordination with the iPresso team or structured data dumps negotiated during scoping. We extract Contacts, Companies, and tag memberships; we preserve lifecycle stage data as a custom field in Nutshell; and we deliver a written inventory of every iPresso workflow, campaign sequence, and channel configuration requiring rebuild by the customer's admin. We do not migrate landing pages, email templates as reusable HTML, or automation logic as executable code.
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 iPresso 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.
iPresso
Contact
Nutshell
Contact
1:1iPresso Contact records map directly to Nutshell Contact. The iPresso lifecycle stage property (e.g., subscriber, lead, customer) is preserved as a custom field nut_ipsso_lifecycle__c in Nutshell for reporting continuity. Standard fields including name, email, phone, address, and owner assignment migrate 1:1. Any behavioral event history (opens, clicks, page views) is summarized as activity note records or stored as a custom long-text field if the customer requires historical event preservation.
iPresso
Company
Nutshell
Account
1:1iPresso Company records map to Nutshell Account. Company name, domain, industry classification, employee count, and address fields migrate 1:1. Account is created before Contact import so that the Account lookup reference is satisfied at the moment of Contact insert. Custom fields on iPresso Company records require field-level mapping to Nutshell custom fields, which are available from the Nutshell Enterprise tier.
iPresso
Tag
Nutshell
Tag (custom field)
lossyiPresso contact segmentation tags migrate to Nutshell as a multi-select text custom field on Contact, or as a dedicated Tag custom field if the customer configures one. Tag names and memberships transfer as comma-separated values or multi-checkbox values depending on the Nutshell plan. The customer selects the tag storage strategy during scoping.
iPresso
Campaign
Nutshell
Campaign
1:1iPresso campaign records containing audience segments, channel assignments, and performance metrics are migrated as Nutshell Campaign records with lookup relationships to the contacts who were members. Campaign performance data (send counts, open rates, click rates) is stored as custom fields on the Nutshell Campaign record. If the customer used iPresso campaign stages or segmentation logic, we document the segment criteria as a written note for the customer to replicate in Nutshell's campaign filtering.
iPresso
Workflow
Nutshell
Workflow (rebuild inventory)
lossyiPresso multi-step workflow sequences do not migrate as executable automation. We extract a written inventory of every active iPresso workflow with its trigger conditions, time delays, actions, and channel assignments, and deliver this as a handoff document for the customer's Nutshell admin to rebuild using Nutshell's automation features. iPresso workflows that reference internal IDs require ID cross-referencing to map correctly after migration.
iPresso
Channel Configuration
Nutshell
Engagement Suite Channels
lossyiPresso channel configurations (Email sender settings, SMS provider credentials, web push configurations) do not migrate directly. We document each iPresso channel with its settings so the customer can reconfigure the equivalent channel in Nutshell's Engagement Suite. Email templates from iPresso can be migrated as HTML content blocks for manual reassignment in Nutshell's template library.
iPresso
Custom Field
Nutshell
Custom Field
1:1Custom properties on iPresso Contacts and Companies map to Nutshell custom fields. Field types are evaluated for direct mapping: text fields map to Nutshell text, picklist values map to Nutshell picklist, date fields map to Nutshell date, and numeric fields map to Nutshell number. Multi-select or checkbox fields require the customer to configure an equivalent field type in Nutshell before migration.
iPresso
Email Template
Nutshell
Email Template
1:1iPresso email template HTML content migrates as content blocks for the customer's admin to reassemble in Nutshell's template library. Dynamic personalization tokens referencing iPresso contact properties require field reference updates in Nutshell's template syntax. We flag any template that contains tokens without direct field equivalents so the customer can address them during the rebuild phase.
| iPresso | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Tag | Tag (custom field)lossy | Fully supported | |
| Campaign | Campaign1:1 | Fully supported | |
| Workflow | Workflow (rebuild inventory)lossy | Fully supported | |
| Channel Configuration | Engagement Suite Channelslossy | Fully supported | |
| Custom Field | Custom Field1:1 | Fully supported | |
| Email Template | Email Template1: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.
iPresso gotchas
No public API documentation or migration tooling
Workflow dependencies can be silently broken at migration cutover
SMS channel and advanced features may be gated by plan tier
Pricing is not published, complicating budget planning
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
Scoping and iPresso extraction coordination
We audit the source iPresso account across custom fields, tag memberships, campaign history, active workflows, and channel configurations. Because iPresso has no public API, we initiate a coordinated data extraction request with the iPresso team or prepare a structured data dump specification. We pair this with a Nutshell edition assessment: Nutshell Foundation ($16/user/month) covers basic contact and pipeline migration; Pro ($42/user/month) adds automation and email sequencing; Enterprise ($67/user/month) is required for custom fields and advanced reporting. The scoping output is a written migration scope, an iPresso data extraction plan, and a Nutshell edition recommendation.
Schema design in Nutshell
We design the destination schema in Nutshell. This includes configuring custom fields (with types mapped from iPresso), tag storage strategy (multi-select field or dedicated tag configuration), and any campaign record types needed to represent iPresso campaign segments. We pre-create all custom fields and validate field types before any data import so that the import encounters no validation failures on the first pass.
Test migration and reconciliation
We run a test migration into a Nutshell trial or sandbox environment using representative data volume. The customer's operations lead reconciles record counts (Contacts in, Accounts in, Campaign members in), spot-checks 20-30 random records against the iPresso source data, and confirms field mapping accuracy before production migration begins. Any mapping corrections happen here, not in production.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from iPresso Companies), Contacts (with Account lookup resolved and lifecycle stage preserved in nut_ipsso_lifecycle__c), tag memberships (as multi-select values on Contact records), Campaigns (as Nutshell Campaign records with member lookups), and activity history (as task and note records). Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, delta sync, and workflow handoff
We freeze iPresso writes during cutover, run a final delta migration of any records created or modified during the migration window, then enable Nutshell as the system of record. We deliver the workflow and automation rebuild inventory document to the customer's Nutshell admin team. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. We do not rebuild iPresso workflows as Nutshell automation sequences inside the migration scope; that work is a separate engagement or an internal admin task.
Platform deep dives
iPresso
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 4 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across iPresso and Nutshell.
Object compatibility
4 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
iPresso: Not publicly documented.
Data volume sensitivity
iPresso 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 iPresso to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your iPresso 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 iPresso
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.