CRM migration

Migrate from iPresso to Nutshell

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

iPresso logo

iPresso

Source

Nutshell

Destination

Nutshell logo

Compatibility

63%

5 of 8

objects map 1:1 between iPresso and Nutshell.

Complexity

CModerate

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

iPresso logo

iPresso

What's pushing teams away

  • API documentation is not publicly accessible and migration tooling is limited, making automated data extraction difficult for teams moving to another platform
  • The interface is feature-dense — reviewers note that some functionalities are difficult to locate without training or occasional assistance from iPresso staff
  • Feature development cycles are slower than global competitors, and support for complex multilingual or international campaigns requires custom configuration
  • No published public API schema, rate limits, or documented export endpoints, creating uncertainty for teams evaluating data portability
  • Documentation and community resources are primarily in Polish, presenting a barrier for non-Polish-speaking teams or global rollouts

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

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

maps to

Nutshell

Contact

1:1
Fully supported

iPresso 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

maps to

Nutshell

Account

1:1
Fully supported

iPresso 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

maps to

Nutshell

Tag (custom field)

lossy
Fully supported

iPresso 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

maps to

Nutshell

Campaign

1:1
Fully supported

iPresso 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

maps to

Nutshell

Workflow (rebuild inventory)

lossy
Fully supported

iPresso 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

maps to

Nutshell

Engagement Suite Channels

lossy
Fully supported

iPresso 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

maps to

Nutshell

Custom Field

1:1
Fully supported

Custom 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

maps to

Nutshell

Email Template

1:1
Fully supported

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

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.

iPresso logo

iPresso gotchas

High

No public API documentation or migration tooling

Medium

Workflow dependencies can be silently broken at migration cutover

Medium

SMS channel and advanced features may be gated by plan tier

Low

Pricing is not published, complicating budget planning

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

  • No public iPresso API requires coordinated data extraction

    iPresso does not publish API documentation, rate limits, or export endpoints publicly. There is no self-service path to programmatically extract Contacts, Companies, or campaign data. We handle this by working with the iPresso team directly to obtain structured data dumps or by using screen-scraping methods where necessary for smaller datasets. We flag this as a high-severity issue during scoping so the customer understands the migration requires manual coordination with iPresso and may extend the timeline by one to two weeks depending on iPresso's responsiveness.

  • Lifecycle stage and behavioral event data require custom field preservation

    iPresso stores contact lifecycle stage and behavioral event history as platform-native properties that have no direct Nutshell equivalent. We preserve lifecycle stage as a custom field nut_ipsso_lifecycle__c on the Contact record and summarize behavioral event history as activity notes or a custom long-text field. The customer should review whether the preserved data meets their reporting needs before cutover, as Nutshell's native activity timeline does not automatically surface iPresso's event-level behavioral data.

  • Workflows and automation sequences do not migrate

    iPresso multi-step workflow sequences reference contacts, tags, channels, and custom fields by internal IDs that change at the destination. We do not migrate workflows as executable code. We deliver a written inventory of every active iPresso workflow with its trigger, conditions, actions, and recommended Nutshell automation equivalent, and the customer's admin rebuilds them post-migration. If workflows are not rebuilt or linked, automated sequences will not fire after cutover.

  • Nutshell's standard Engagement Suite features may require a paid add-on

    Nutshell's Engagement Suite (email marketing, web chat, automation features) is a separate paid add-on to the core CRM. Teams migrating from iPresso's bundled multi-channel capabilities may need to purchase the Engagement Suite separately in Nutshell. We identify which iPresso channels (Email, SMS, Web Push) were in active use and map them to the equivalent Nutshell Engagement Suite feature, flagging any capability gaps before migration so the customer can plan the appropriate Nutshell subscription tier.

Migration approach

Six steps for a successful iPresso to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

iPresso logo

iPresso

Source

Strengths

  • Multi-channel communication including SMS, email, web push, and print in a unified platform
  • Continuous product development driven by direct customer feature requests
  • Drag-and-drop workflow builder for multi-step marketing automation sequences
  • Strong Polish-language support and documentation for Central European teams
  • Industry-specific solutions for finance, automotive, retail, FMCG, and travel sectors

Weaknesses

  • No publicly documented API schema or migration/export tooling
  • Published pricing tiers are not accessible on the website, requiring sales contact
  • Documentation and community resources are primarily in Polish
  • Feature set can be overwhelming for small teams without dedicated marketing ops resources
  • Limited international third-party integration ecosystem compared to global competitors
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?

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

C

Overall complexity

Moderate migration

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

  • Object compatibility

    C

    4 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

    iPresso: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most migrations land between three and five weeks for accounts under 15,000 Contacts and 3,000 Companies with standard field mapping and straightforward iPresso data extraction. Migrations requiring coordinated data dumps with the iPresso team, multi-segment campaign history preservation, or custom field-heavy schemas move to six to ten weeks because of extraction complexity and field mapping scope. Timeline assumes the customer can provide iPresso data within one to two weeks of request; delays from iPresso's side extend the overall timeline.

Adjacent paths

Related migrations to explore

Ready when you are

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