How long does an Xtremepush to Nutshell migration take?

Most migrations land between two and four weeks for accounts under 15,000 People, 3,000 Companies, and straightforward engagement histories without loyalty state or complex gamification mechanics. Migrations with large engagement volumes (over 200,000 activity records), loyalty points and tier data requiring transformation, or Nutshell Enterprise API provisioning coordination for integration wiring move to five to eight weeks because of batch chunking, attribute mapping, and coordination overhead.

Do Xtremepush campaigns, segments, and workflows migrate to Nutshell?

No. Xtremepush campaigns, audience segments, and workflow automations are engagement-layer objects with no equivalent in Nutshell. Nutshell does not have a campaign execution log, a dynamic segment builder, or a workflow automation engine for multi-step engagement journeys. We export campaign metadata and segment membership rules as JSON reference files, and we deliver a written inventory of active workflows and gamification mechanics for the customer's admin to evaluate for rebuild in a dedicated engagement platform.

What does an Xtremepush to Nutshell migration typically cost?

Migrations under 15,000 People, 3,000 Companies, and no complex loyalty or gamification state land between $3,500 and $5,500. Migrations with large engagement histories, loyalty points and tier data, or integration wiring to Nutshell Enterprise API move to $7,500-$11,000. Nutshell subscription cost ($16-$79/user/month depending on tier) begins post-migration and sits outside the migration fee. Xtremepush does not charge an exit fee, but any outstanding contract terms are between the customer and Xtremepush directly.

Can we keep Xtremepush for push and SMS while moving CRM data to Nutshell?

Yes. A hybrid pattern is common where Xtremepush continues to handle push notifications, SMS, and email campaigns while Nutshell manages the sales CRM (People, Companies, Deals, pipeline). In this scenario, we migrate People and activity history to Nutshell, and the customer maintains Xtremepush for engagement. We export device token data as a CSV so that Xtremepush push subscriptions can remain active. The customer evaluates consolidating engagement onto a single platform later if managing two systems becomes overhead.

What happens to Xtremepush loyalty points and gamification data?

Loyalty points, tier assignments, and gamification achievements are exported as snapshot values and mapped to custom fields on Nutshell People. The current points balance and tier name transfer; the gamification rule engine (promotion triggers, reward thresholds, achievement definitions) is not exposed via export and cannot migrate. We provide a structured inventory of all observed gamification mechanics during discovery so the customer can document the rules for a rebuild in a loyalty platform if needed.

Do we lose engagement history (calls, emails, meetings) during migration?

No. Engagement records migrate to Nutshell Activities linked to the corresponding People record. Calls transfer as Activity Call records with duration; emails transfer as Activity Email records with subject and body; meetings transfer as Activity Meeting records with time and attendee list; tasks transfer as Activity Task records with status and due date. We resolve People records by email match and flag any engagement records with unmatched email addresses for the customer's admin to reconcile.

Does Xtremepush push token and device data migrate?

No. Nutshell is a sales CRM with no push notification or SMS capability, so device tokens, device type, OS version, and push subscription status cannot be stored in Nutshell. We export device token data as a CSV reference file for the customer's records. If the customer continues using a push provider alongside Nutshell, the CSV can be used for token re-registration. Location data (geofences, iBeacons) is similarly exported as a CSV reference file and cannot land in Nutshell's schema.

What Nutshell tier do we need for this migration?

Nutshell Foundation ($16/user/month) supports the core migration: People, Companies, Deals, Activities, and custom fields. Nutshell Pro ($42/user/month) is required if the migration includes API-based integration wiring (ETL tool connections, data warehouse sync). Nutshell Enterprise ($67/user/month) is required if the customer needs read-only SQL access, advanced SSO, or scheduled API access beyond what Pro provides. We confirm the required tier during discovery based on the customer's integration and reporting requirements.

Xtremepush to Nutshell Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Moving from Xtremepush to Nutshell is a platform-category shift from engagement automation and CDP to sales CRM. Xtremepush consolidates user profiles, device tokens, push campaigns, loyalty state, and behavioral events in one engagement layer. Nutshell is a structured sales CRM that manages People, Companies, Leads, Deals, and Activities with pipeline automation and reporting. We migrate the CRM-record subset (People contact fields, Companies, custom attributes, activity history) and flag the engagement-layer data that cannot land in a sales CRM: push tokens, SMS history, location data, loyalty points, gamification mechanics, and campaign execution records. Workflows, audience segments, and automated export schedules do not migrate; we deliver a written inventory of each for the customer's admin to evaluate for rebuild in Nutshell or a separate engagement tool.

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

Xtremepush

What's pushing teams away

MFA lockout risk: if a user loses their phone or authenticator app, login becomes blocked and recovery can be slow, disrupting team access during critical campaign windows.
Steep initial learning curve: the interface is described as overwhelming for new users until they build familiarity with where campaigns, segments, and attributes are configured.
Limited message builder flexibility: more flexible editing options in the drag-and-drop composer are frequently requested, with some users resorting to workarounds for complex personalization scenarios.
Point solution lock-in risk: brands with multi-vendor stacks cite complexity in keeping engagement data synchronized across Xtremepush and other platforms in real time.

Choosing

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

Each row shows how a Xtremepush 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.

Xtremepush

User Profiles

maps to

Nutshell

People

1:1

Fully supported

Xtremepush user profiles map to Nutshell People. We extract the profile identifier, name fields (first name, last name), email address, phone number, and any custom attributes stored as key-value pairs. The Xtremepush profile ID is preserved as a custom field xtremepush_id__c for reconciliation and cross-reference. Consent status (subscribed/unsubscribed) migrates as a custom field or Nutshell's native opt-out flag. HubSpot-style multi-value tags from Xtremepush migrate to Nutshell custom fields defined as multi-select picklists during schema setup.

Xtremepush

Company data

maps to

Nutshell

Company

1:1

Fully supported

Xtremepush does not have a native company object, but profile records may contain organization or company name fields. We extract any company name, domain, or organization identifier from Xtremepush profiles and create Nutshell Company records, linking each to the corresponding People record. If Xtremepush has a separate company export, we map it directly to Nutshell Company with address and industry fields preserved.

Xtremepush

Attributes and Tags

maps to

Nutshell

Custom Fields (People, Company, Lead)

lossy

Fully supported

Xtremepush user profile attributes are exported as key-value pairs. We define Nutshell custom fields of matching types (text, number, date, currency, dropdown) for each attribute observed during discovery. Tags (multi-value) are mapped to Nutshell multi-select picklist fields. We document the full attribute schema during discovery and pre-create fields in Nutshell before any data loads begin.

Xtremepush

Preferences and Consent Records

maps to

Nutshell

People (opt-out field)

1:1

Mapping required

Xtremepush consent records include preference type (Marketing, Legitimate Interest), subscription status, last-updated timestamp, and consent source. We map the subscription status to Nutshell's HasOptedOutOfEmail standard field and preserve the full preference type and source in a custom field consent_type__c for compliance audit. Note that Xtremepush consent exports do not include historical consent changes or campaign-channel context; we flag records with only import-source consent and recommend re-collection for regulated industries.

Xtremepush

Engagements: Calls

maps to

Nutshell

Activities (Call)

1:1

Fully supported

Xtremepush call engagement records (timestamp, duration, disposition, notes) map to Nutshell Activities of type Call linked to the corresponding People record. Call duration in seconds transfers to a custom duration field. We resolve the People record by email match before inserting the activity.

Xtremepush

Engagements: Emails

maps to

Nutshell

Activities (Email)

1:1

Fully supported

Xtremepush email engagement records (subject, body, timestamp, direction) map to Nutshell Activities of type Email linked to the corresponding People record. Email direction (sent/received) migrates as a custom field. We extract the most recent email thread per contact to avoid overwhelming Nutshell's activity timeline with every single email event.

Xtremepush

Engagements: Meetings

maps to

Nutshell

Activities (Meeting)

1:1

Fully supported

Xtremepush meeting engagement records (title, scheduled time, attendees, location) map to Nutshell Activities of type Meeting. Start time, end time, and location transfer directly. Attendee email addresses are matched to Nutshell People records to link attendees; unmatched attendees are noted in a custom field for reconciliation.

Xtremepush

Engagements: Tasks

maps to

Nutshell

Activities (Task)

1:1

Fully supported

Xtremepush task engagement records migrate to Nutshell Activities of type Task. Status, due date, priority, and task text transfer directly. Owner resolution is by email match to Nutshell users; tasks assigned to unmatched owners are queued for admin reconciliation.

Xtremepush	Nutshell	Compatibility
User Profiles	People1:1	Fully supported
Company data	Company1:1	Fully supported
Attributes and Tags	Custom Fields (People, Company, Lead)lossy	Fully supported
Preferences and Consent Records	People (opt-out field)1:1	Mapping required
Engagements: Calls	Activities (Call)1:1	Fully supported
Engagements: Emails	Activities (Email)1:1	Fully supported
Engagements: Meetings	Activities (Meeting)1:1	Fully supported
Engagements: Tasks	Activities (Task)1:1	Fully supported

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.

Xtremepush gotchas

High

Push token migration requires coordinated SDK update and dev team handoff

Medium

Consent preference export does not include full audit trail

Medium

Location services require separate paid activation and SDK changes

Low

Loyalty and gamification state is profile-relative, not independently exportable

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

Xtremepush gotchas		Nutshell gotchas
Severity	Issue	Severity	Issue
High	Push token migration requires coordinated SDK update and dev team handoff	High	Contact tier limits enforced on import
Medium	Consent preference export does not include full audit trail	Medium	No bulk API endpoint requires paginated extraction
Medium	Location services require separate paid activation and SDK changes	Medium	Email sequences not exportable via API
Low	Loyalty and gamification state is profile-relative, not independently exportable	Medium	Foundation plan disables key sales features

Pair-specific challenges

Push tokens and device data have no Nutshell equivalent

Xtremepush stores device tokens (APNS, Firebase GCM) linked to user profiles. Nutshell is a sales CRM with no push or SMS capability, so device tokens, device type, OS version, and push subscription status cannot land in any standard or custom Nutshell field. We export a CSV of device token data as a reference file for the customer's records but do not load it into Nutshell. If the customer continues using a push provider alongside Nutshell, the push token export is handed off for re-registration.
Campaigns and audience segments are engagement-layer objects

Xtremepush campaigns (push, SMS, email execution records) and audience segments (dynamic behavioral rules) have no equivalent in Nutshell. Nutshell does not have a campaign object, a segment builder, or a message execution log. We export campaign metadata and segment membership rules as JSON reference files for the customer's admin to evaluate for rebuild in a dedicated engagement platform (Braze, Mailchimp, HubSpot Marketing, or Salesforce Marketing Cloud Engagement). Campaign content does not migrate.
Loyalty and gamification state is profile-attached and non-exportable as a ledger

Xtremepush stores loyalty points, tier assignments, and gamification achievements as attributes on user profiles rather than as a standalone loyalty ledger. We export the current state snapshot (points balance, tier name, earned achievements) as custom field values on Nutshell People during migration. The gamification rule engine, reward triggers, and promotion mechanics are not exposed via export and cannot be migrated. We provide a structured inventory of all observed gamification mechanics during discovery for the customer to document for a loyalty platform rebuild.
Location data (geofences and iBeacons) cannot migrate to Nutshell

Xtremepush stores geofence and iBeacon location metadata (coordinates, radius, beacon UUIDs) as location objects linked to user profiles. Nutshell has no location or spatial data fields. We export location metadata as a CSV reference file for cases where the customer uses a separate location intelligence tool. Location permission state is tied to the Xtremepush SDK and cannot be re-established in Nutshell; this is a post-migration step for the customer's app team if location tracking continues.
Xtremepush automated export schedules do not map to Nutshell

Xtremepush SFTP-based automated exports (hourly, daily, weekly, monthly) are configured for data warehouse or BI tool consumption. Nutshell does not have a native SFTP export scheduler. We document the existing export schedule, credential paths, and exported schema as part of the migration handoff. The customer's data team evaluates whether a Nutshell REST API integration or a third-party ETL tool (e.g., Census, Hightouch, Zapier) replaces the automated export schedule.

Migration approach

Six steps for a successful Xtremepush to Nutshell data migration

Discovery and data audit

We audit the Xtremepush account to establish the full record inventory: People count, Company/organization data, engagement record types and volumes (calls, emails, meetings, tasks), attribute and tag schema, consent preference types, loyalty state snapshot, location data presence, and campaign count. We also identify automated export schedules and any SFTP credential configurations. The discovery output is a written data inventory and a migration scope that explicitly separates CRM-record data (which migrates) from engagement-layer data (which is exported as reference files or flagged as non-migratable).
Schema design in Nutshell

We design the Nutshell destination schema before any data loads begin. This includes creating custom fields on People, Company, and Lead objects for Xtremepush attributes and tags that do not map to standard Nutshell fields (multi-select picklists for tags, text and date fields for custom attributes). We define a custom field xtremepush_id__c on People to preserve the source profile ID for reconciliation. If the customer is on Nutshell Foundation tier, we note that custom fields are supported but API access requires Pro or Enterprise; we coordinate tier provisioning if needed.
Sandbox validation and record reconciliation

We run a sandbox migration into a Nutshell test environment using a representative data sample. The customer reconciles record counts (People imported, Companies imported, Activities attached), spot-checks 20-30 records against the Xtremepush source, and validates that custom field values populated correctly. Any missing attribute mappings or data quality issues (duplicate People, unmatched Companies) are resolved before production migration begins.
Owner and user reconciliation

We extract every distinct Xtremepush user or agent referenced on engagement records and match by email against Nutshell Users. Any unmatched owner references go to a reconciliation queue for the customer's admin to provision in Nutshell before activity records are loaded, because Nutshell Activity records require an OwnerId reference.
Production migration in dependency order

We run production migration in record-dependency order: Companies first (to establish Account-level records), People second (with xtremepush_id__c and custom field values), Activities third (calls, emails, meetings, tasks linked to People by email match). Each phase emits a reconciliation report before the next begins. Engagement-layer reference exports (device tokens, campaigns, location data, loyalty state) are generated as CSV and JSON files and handed off alongside the migration report.
Cutover, validation, and engagement-layer handoff

We freeze Xtremepush writes during the cutover window, run a final delta migration of any records modified during migration, then enable Nutshell as the system of record for CRM data. We deliver the engagement-layer reference files and the gamification inventory document to the customer's admin. We support a three-day hypercare window for reconciliation issues. We do not rebuild Xtremepush workflows, segments, or campaigns in Nutshell; those are outside the migration scope and require either manual rebuild or a separate engagement scope.

Platform deep dives

Context on both ends of the pair

Xtremepush

Source

Strengths

Multichannel unification: push, SMS, email, and web push managed from a single campaign canvas without switching tools.
Real-time triggering: SDK-based event collection supports in-session automation rather than batch-only campaigns.
AI-driven audience recommendations with Explainable AI, providing justification for segment selections.
Gamification and loyalty mechanics built natively, not bolted on via third-party plugins.
SFTP-based automated exports allow programmatic data extraction on flexible schedules.

Weaknesses

No publicly documented API rate limits or bulk endpoint specifications, making migration pacing unpredictable without a technical scoping call.
Push token migration from legacy providers requires manual CSV export and Xtremepush dev team involvement, adding coordination overhead.
Enterprise features (encrypted push, location services) are separately priced add-ons negotiated with account management, not self-serve.
Message builder flexibility is limited compared to dedicated email or creative tools, prompting some teams to author content elsewhere and import.

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

	Xtremepush Source	Nutshell Destination
Strengths	Multichannel unification: push, SMS, email, and web push managed from a single campaign canvas without switching tools. Real-time triggering: SDK-based event collection supports in-session automation rather than batch-only campaigns. AI-driven audience recommendations with Explainable AI, providing justification for segment selections. Gamification and loyalty mechanics built natively, not bolted on via third-party plugins. SFTP-based automated exports allow programmatic data extraction on flexible schedules.	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	No publicly documented API rate limits or bulk endpoint specifications, making migration pacing unpredictable without a technical scoping call. Push token migration from legacy providers requires manual CSV export and Xtremepush dev team involvement, adding coordination overhead. Enterprise features (encrypted push, location services) are separately priced add-ons negotiated with account management, not self-serve. Message builder flexibility is limited compared to dedicated email or creative tools, prompting some teams to author content elsewhere and import.	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.

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Xtremepush 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
Xtremepush: Not publicly documented.
Data volume sensitivity
A
Xtremepush exposes a bulk API — large-volume migrations stream efficiently.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Xtremepush to Nutshell

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Xtremepush

Nutshell

How Xtremepush objects map to Nutshell

What specifically takes care here

Six steps for a successful Xtremepush to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Xtremepush to Nutshell migration cost

What are you migrating?

Frequently asked questions about Xtremepush to Nutshell data migrations

Can't find your answer?

Related migrations to explore

Move from Xtremepush.
Land in Nutshell, intact.

Migrate from Xtremepush to Nutshell

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Xtremepush

Nutshell

How Xtremepush objects map to Nutshell

What specifically takes care here

Six steps for a successful Xtremepush to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Xtremepush to Nutshell migration cost

Frequently asked questions about Xtremepush to Nutshell data migrations

Can't find your answer?

How long does an Xtremepush to Nutshell migration take?

Do Xtremepush campaigns, segments, and workflows migrate to Nutshell?

What does an Xtremepush to Nutshell migration typically cost?

Can we keep Xtremepush for push and SMS while moving CRM data to Nutshell?

What happens to Xtremepush loyalty points and gamification data?

Do we lose engagement history (calls, emails, meetings) during migration?

Does Xtremepush push token and device data migrate?

What Nutshell tier do we need for this migration?

Related migrations to explore

Move from Xtremepush. Land in Nutshell, intact.

Move from Xtremepush.
Land in Nutshell, intact.