CRM migration

Migrate from eTrigue to Nutshell

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

eTrigue logo

eTrigue

Source

Nutshell

Destination

Nutshell logo

Compatibility

63%

5 of 8

objects map 1:1 between eTrigue and Nutshell.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from eTrigue DemandCenter to Nutshell is a migration from a campaign-centric marketing automation tool into a full CRM with deal and account management. eTrigue organizes data around Prospects and Campaigns with no native Deals, Accounts, or Opportunities; Nutshell uses Contacts, Organizations (Accounts), Leads, and Deals as first-class objects. We extract via eTrigue's built-in CSV export tool, decode the numeric Status field codes (1 = Active, 2 = Opt-Out), map each of the five Lead Score sub-components to individual custom fields on the Nutshell Contact, and load into Nutshell via the REST API. We do not migrate Landing Pages, Progressive Forms, or partner channel program structures as functional assets; we deliver a written field-level inventory for manual rebuild. Workflows and automations in eTrigue do not have a Nutshell equivalent and are outside migration scope.

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

eTrigue logo

eTrigue

What's pushing teams away

  • Workflow and automation capabilities are considered limited compared to broader platforms, with one reviewer noting they switched specifically because 'workflow and automation capabilities were a bit limited compared to other software on the market.'
  • UX and UI frustrations accumulate over time — users report 'minor UX frustrations when it came to renaming or reorganizing things,' creating friction for power users managing many campaigns.
  • The platform is perceived as better suited for small to medium teams, leading larger organizations to migrate toward enterprise-grade marketing automation with richer data models.
  • Pricing is opaque and quoted per-demo, which creates uncertainty and drives some buyers toward platforms with published tier-based pricing.

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

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

eTrigue

Prospect

maps to

Nutshell

Contact

1:1
Fully supported

eTrigue Prospects map 1:1 to Nutshell Contacts. Standard fields (name, email, company, phone) export cleanly from the Prospects list CSV and load into the Contact object via Nutshell API. First name and last name are split from the full Prospect name during the transform phase. The prospect's Organization is resolved by matching the exported company field against Nutshell Organizations, creating the Organization if it does not exist, and linking Contact to it via the primary_organization_id field.

eTrigue

Prospect Status field

maps to

Nutshell

Contact email_opt_in flag

lossy
Fully supported

eTrigue exports the Status field as numeric codes (e.g., 1 = Active, 2 = Opt-Out) rather than human-readable labels. We decode these codes during data profiling before any import. Active prospects map to email_opt_in = true; Opt-Out and other codes map to email_opt_in = false. Without this decoding step, all records import as active, silently unsubscribing no one.

eTrigue

Lead Score sub-components

maps to

Nutshell

Contact custom numeric fields

lossy
Fully supported

eTrigue stores five separate Lead Score sub-components as numeric fields on the Prospect: Campaign Score, Activity Score, Source Score, Relationship Score, and Buy Time Score. Nutshell has no native equivalent scoring model. We create five custom numeric fields on the Contact object (campaign_score__c, activity_score__c, source_score__c, relationship_score__c, buytime_score__c) before import and load each sub-score individually. The composite total can be reconstructed as a formula field or used by the customer's scoring logic post-migration.

eTrigue

3D Lead Scoring composite value

maps to

Nutshell

Contact custom numeric field

1:1
Fully supported

eTrigue's 3D Lead Scoring model enriches the standard 5-component score with content-type engagement weighting. We export the composite 3D score as a single numeric value and store it in a custom field (score_3d__c) on the Nutshell Contact. This preserves the enriched scoring signal for customers who used 3D scoring to rank prospect quality. Destination scoring logic is the customer's responsibility post-migration.

eTrigue

Campaign

maps to

Nutshell

Campaign

1:1
Fully supported

eTrigue Campaigns map to Nutshell Campaigns. Campaign name, start date, and campaign type migrate. Email send history and response data (opens, clicks, bounces) from eTrigue's campaign reporting exports are loaded into Nutshell Campaign Members and campaign activity notes. Nutshell Campaigns track mailing lists and email sends rather than automated nurture journeys, so the campaign response timeline is preserved but the workflow logic is not.

eTrigue

Activity History

maps to

Nutshell

Activity (Task)

1:1
Fully supported

eTrigue records page views, email opens, form submissions, and campaign responses with timestamps on the Prospect's Activity History tab. We export this as a structured activity log and map it to Nutshell Activities (Task records) linked to the Contact. Each activity type is tagged by category (page_view, email_open, form_submission, campaign_response) in the activity_notes field so the timeline is readable in Nutshell. Activity timestamps are preserved as the Task due date and creation date.

eTrigue

Custom Fields (Boolean, Text, Number)

maps to

Nutshell

Contact custom fields

lossy
Fully supported

eTrigue supports Boolean, Text, Number, and other custom field types under Settings > Prospect Settings > Prospect Fields. We create matching custom fields on the Nutshell Contact object before import. Boolean fields with custom labels (e.g., 'Has Demo Scheduled: Yes / No') map to Nutshell Boolean custom fields. Text fields map to String custom fields. Number fields map to Numeric custom fields. All field definitions and label mappings are documented in the field inventory delivered before import.

eTrigue

Partner/Channel Program data

maps to

Nutshell

Organization or Contact custom field

1:1
Fully supported

eTrigue Lead Accelerator customers store partner organization names and campaign attribution in custom Prospect fields rather than a native Partner object. We map these to either the Nutshell Organization (if the partner organization is the primary account) or a custom Contact field (partner_name__c or partner_campaign__c) depending on the customer's data model. Partner-specific scoring rules that exist in eTrigue are documented for manual recreation in Nutshell rules post-migration.

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.

eTrigue logo

eTrigue gotchas

High

No public API means migration relies on CSV export only

Medium

Opt-Out status encoding in Status field export

Medium

Lead Score sub-components are five separate fields, not one

Medium

Partner program data stored in custom fields, not a native object

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 API forces all extraction through CSV export

    eTrigue does not publish a REST or SOAP API for programmatic data access. All migration extraction uses the built-in CSV export from the Prospects list or Scheduled Exports. Large databases may require multiple export batches with pagination using saved search filters. We assemble the full dataset from these batches before loading into Nutshell. This manual-intensive process adds time compared to API-based migrations and requires the customer to have CSV export access in eTrigue. Any records not visible in the exported search criteria are excluded unless the customer provides an expanded export.

  • Status field exports as numeric codes, not labels

    eTrigue's Status field exports as numeric codes rather than human-readable text. Support documentation confirms that Status values (e.g., 1 = Active, 2 = Opt-Out) require decoding before import. We detect and decode these codes during data profiling and map them to Nutshell's email_opt_in flag. Migrations that skip this step silently import all records as active, effectively clearing the opt-out list. We flag this as the first transform step in the data pipeline.

  • Five Lead Score sub-components require field-by-field mapping

    eTrigue's composite Lead Score is stored as five separate numeric properties (Campaign, Activity, Source, Relationship, Buy Time), not a single score field. Nutshell has no native multi-component scoring model. We export all five sub-scores individually and create five custom numeric fields on the Nutshell Contact object before import. The destination's scoring formula must be rebuilt manually post-migration using Nutshell's workflow rules or a third-party scoring tool.

  • Landing pages and progressive forms do not migrate

    eTrigue landing pages built in its editor and the progressive form field definitions do not have a functional equivalent in Nutshell. Nutshell does not include a landing page builder or progressive form engine. We export form field definitions as a written field inventory mapping each eTrigue field to Nutshell's web-to-contact form field (or a third-party form tool the customer selects). Landing page styling and layout are outside scope and require a rebuild in the customer's chosen form or web platform.

  • Partner program data stored as custom fields requires schema decision

    Customers using eTrigue Lead Accelerator for channel partner programs store partner attribution and partner-specific campaign data in custom Prospect fields rather than a dedicated Partner object. These custom fields must be mapped to either Nutshell Organizations (if the partner is the primary account) or custom Contact fields. We document the customer's chosen mapping during discovery and flag any partner-specific scoring rules that cannot be preserved in Nutshell's standard schema without a separate partner management setup.

Migration approach

Six steps for a successful eTrigue to Nutshell data migration

  1. Discovery and CSV export assembly

    We audit the eTrigue portal for prospect volume, active campaign count, custom field definitions, 3D Lead Scoring configuration, and any partner program custom fields. We identify the CSV export batches required to capture all Prospects and Activity History using saved search filters, since the lack of a public API requires manual export coordination with the customer. The discovery output is a written migration scope with a full field inventory listing every source field, its type, and its proposed Nutshell destination.

  2. Status code decoding and data profiling

    We run a data profiling pass on the exported CSV before any import. This step decodes the numeric Status field values to their human-readable equivalents and flags any records with non-standard status codes that require manual review. We also profile email deliverability fields (bounce flags, unsubscribe flags) to ensure they map correctly to Nutshell's email_opt_in behavior. The profiling output is a data quality report shared with the customer for approval before import begins.

  3. Nutshell schema configuration

    We create the custom Contact fields in Nutshell before any data import. This includes five numeric fields for the Lead Score sub-components (campaign_score__c, activity_score__c, source_score__c, relationship_score__c, buytime_score__c), a custom field for the 3D composite score (score_3d__c), a Boolean field for any Boolean custom fields from eTrigue, and any partner attribution fields (partner_name__c, partner_campaign__c). We use the Nutshell API to create fields. The customer approves the field configuration before record migration begins.

  4. Organization and Contact import

    We import records in dependency order. First, we extract unique Organization names from the exported Prospect company field and create Nutshell Organizations for each. Then we import Contacts with the Organization relationship resolved via the primary_organization_id field. The five Lead Score sub-components load into the corresponding custom numeric fields. The 3D composite score loads into score_3d__c. Status codes decode to email_opt_in during this phase. Each import batch emits a reconciliation count (records in, records created, records updated, records rejected) before the next phase begins.

  5. Campaign and Activity History migration

    We import eTrigue Campaigns into Nutshell Campaigns, then load the Activity History from the Prospect export as Nutshell Activity records (Tasks) linked to the corresponding Contact. Activity type (page_view, email_open, form_submission, campaign_response) is stored in the activity notes field. Timestamps are preserved as the Task due date. For customers with large activity histories, we batch the activity import to avoid API rate limit responses from Nutshell and use exponential backoff on any 429 responses.

  6. Cutover, validation, and rebuild handoff

    We freeze writes in eTrigue during the cutover window and run a final delta migration of any records modified during the migration window. We validate by reconciling record counts (Contacts imported vs. Prospects exported, Activities imported vs. Activity History rows exported) and spot-checking 20-30 records against the source export. We deliver the field inventory, Status code mapping reference, and a written note of any eTrigue automations and landing pages that require manual rebuild in the customer's chosen tools. We do not rebuild automations or forms inside the migration scope.

Platform deep dives

Context on both ends of the pair

eTrigue logo

eTrigue

Source

Strengths

  • Drag-and-drop campaign builder reduces onboarding time for non-technical marketing users.
  • Lead scoring model is multi-dimensional (5-component composite) and praised for accuracy in G2 reviews.
  • Built-in progressive forms capture prospect data contextually within campaigns.
  • Support responsiveness is a documented strength — callbacks within an hour for complex setups.
  • Partner marketing specialization with Lead Accelerator is a differentiator for channel-focused organizations.

Weaknesses

  • Limited workflow and automation capabilities compared to broader marketing automation platforms.
  • No publicly documented API — all data extraction relies on the built-in CSV export tool, which constrains migration speed.
  • Platform is perceived as scaling poorly beyond small to medium team sizes.
  • Pricing is opaque (per-demo quote model) with no published tier-based pricing, complicating budget planning.
  • UX frustrations with renaming and reorganizing objects accumulate for power users managing many campaigns.
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. 2 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 eTrigue and Nutshell.

  • Object compatibility

    B

    2 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

    eTrigue: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your eTrigue 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 two and four weeks for accounts under 5,000 Prospects with standard fields and no partner program custom fields. Migrations with large activity histories (over 100,000 engagement records), multiple 3D scoring models, or partner program data stored across many custom fields move to four to eight weeks because of multi-batch CSV assembly, data profiling for Status code decoding, and the field-by-field scoring reconstruction. The lack of a public API on the eTrigue side means export preparation is a customer-assisted step that affects the timeline.

Adjacent paths

Related migrations to explore

Ready when you are

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