CRM migration
Field-level mapping, validation, and rollback between Right On Interactive and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Right On Interactive
Source
Nutshell
Destination
Compatibility
5 of 9
objects map 1:1 between Right On Interactive and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Right On Interactive is a lifecycle-based marketing automation platform with 3D scoring across behavioral, demographic, and firmographic dimensions, but it lacks a publicly documented API for direct data extraction. Migrating to Nutshell means shifting from a marketing-automation-centric model to a sales CRM-centric model where lifecycle stages, 3D scores, and behavioral segmentation must be preserved as custom fields rather than native platform features. We coordinate with Right On Interactive's data export process to retrieve contacts, companies, engagement history, and account-configured lifecycle stage labels, then map them into Nutshell's Person, Account, Lead, and custom field structure. Active email automation workflows and lifecycle-triggered campaigns do not migrate; we deliver a written playbook documenting each automation's trigger logic for the customer's team to rebuild in Nutshell or a dedicated marketing automation layer.
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 Right On Interactive 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.
Right On Interactive
Contact
Nutshell
Person (Contacts API)
1:1Right On Interactive Contacts map to Nutshell Person records via the Contacts API endpoint. Each Contact carries a lifecycle stage label (account-configured, e.g., 'Prospect', 'MQL', 'Customer') that we capture as a custom field on Person rather than relying on Nutshell's native status, which is tied to the Lead lifecycle. The contact's primary email, phone, address, title, and owner assignment migrate directly. HubSpot-style owner-to-Nutshell-user resolution happens by email match; any owner without a matching Nutshell user is flagged in a reconciliation queue for admin provisioning.
Right On Interactive
Account/Company
Nutshell
Account (Companies API)
1:1Right On Interactive Accounts store firmographic data used in 3D scoring (company size, industry, revenue tier). These map to Nutshell Account records via the Companies API. The account domain and website become the dedupe key for matching against existing Nutshell Accounts during import. We create Accounts before Person records so that the account_id reference is resolved at Person insert time, avoiding orphaned persons without an account link.
Right On Interactive
Lifecycle Stage
Nutshell
Custom Field on Person
lossyRight On Interactive lifecycle stage names are account-configured custom labels, not fixed platform values. We capture the full stage label set during discovery and create a matching custom picklist field on Person before migration. Each contact's stage label maps to the corresponding picklist value in Nutshell. If the destination Nutshell account uses Leads for unqualified prospects, contacts at 'Lead' or 'Prospect' stage may alternatively map to Lead records; this is decided during scoping based on the customer's sales process.
Right On Interactive
3D Scores (Behavioral, Demographic, Firmographic)
Nutshell
Custom Number Fields on Person
lossyRight On Interactive's 3D scoring produces three sub-scores (behavioral, demographic, firmographic) plus an aggregate score. Nutshell's native scoring applies to Leads only on paid tiers and stores a single numeric value. We export all three sub-scores as individual custom number properties on Person (e.g., roi_behavioral_score__c, roi_demographic_score__c, roi_firmographic_score__c) and place the aggregate score in Nutshell's native lead_score field if the contact maps to a Lead, or in a custom aggregate field if it maps to a Person. This preserves the analytical dimension while maintaining compatibility with Nutshell's segmentation tools.
Right On Interactive
Lead
Nutshell
Lead
1:1Right On Interactive Leads (synced from CRM integrations) map directly to Nutshell Lead records. Lead source attribution, initial scoring at time of sync, and lead status migrate as Lead custom fields. If the customer uses Nutshell Leads as a separate record type for unqualified prospects, we route contacts with early lifecycle stages (e.g., 'Lead', 'Prospect') to Lead; contacts with qualified stages (e.g., 'SQL', 'Customer') route to Person attached to an Account.
Right On Interactive
Engagement: Email Opens, Clicks, Form Submissions
Nutshell
Activity on Person
1:1Right On Interactive engagement events (email opens, link clicks, form submissions, page visits) migrate as Activity records attached to the corresponding Person in Nutshell. Each activity gets a type (Email Open, Form Submit, etc.), a timestamp, and a reference to the campaign or program that generated it. Activity data is written via Nutshell's API in batched requests; we throttle to avoid rate limits on find requests and use stub responses where full detail is not required for the activity log.
Right On Interactive
Opportunity
Nutshell
Lead (Nurture Track) or Custom Field
lossyRight On Interactive Opportunity data synced from CRM integrations does not have a direct Nutshell equivalent because Nutshell's core CRM model centers on Person and Account with pipeline management through its own deal tracking. If the customer's Right On Interactive instance contains active opportunity records with stage and value data, we map these to Nutshell Lead records with a custom opportunity_value__c field and a nurture_track custom field, or we flag them for a separate CRM migration if the customer is moving to a full CRM from Nutshell simultaneously.
Right On Interactive
Event Registrations
Nutshell
Activity + Custom Field on Person
1:1Event and webinar registrations including invitation status, attendance records, and follow-up sequence assignments migrate as Person activities with a custom event_type field distinguishing between registration, attendance, and no-show states. The Nutshell user assigned to the registration migrates as the activity owner. Follow-up task assignments migrate as Task records linked to the Person.
Right On Interactive
Campaign/Program Metadata
Nutshell
Custom Field on Activity
lossyRight On Interactive campaign records include program assets, budgets, and multi-channel assignments that do not map to Nutshell's native objects. We migrate campaign name, campaign type, and status as custom fields on the Activity records that represent campaign-triggered engagements. Active execution state and campaign budgets require separate documentation and rebuild in Nutshell or a dedicated marketing automation layer.
| Right On Interactive | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person (Contacts API)1:1 | Fully supported | |
| Account/Company | Account (Companies API)1:1 | Fully supported | |
| Lifecycle Stage | Custom Field on Personlossy | Fully supported | |
| 3D Scores (Behavioral, Demographic, Firmographic) | Custom Number Fields on Personlossy | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Engagement: Email Opens, Clicks, Form Submissions | Activity on Person1:1 | Fully supported | |
| Opportunity | Lead (Nurture Track) or Custom Fieldlossy | Fully supported | |
| Event Registrations | Activity + Custom Field on Person1:1 | Fully supported | |
| Campaign/Program Metadata | Custom Field on Activitylossy | 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.
Right On Interactive gotchas
No publicly documented API for direct data extraction
Lifecycle stage names are account-configured custom fields
3D scoring sub-dimensions do not map to standard CRM score fields
Email automation workflows require manual rebuild on destination platform
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
Export coordination and discovery
We initiate contact with Right On Interactive to coordinate data export, confirming which objects are available (Contacts, Accounts, Leads, Engagement History, Campaigns) and the export format. We audit the source data for contact volume, engagement history depth, lifecycle stage label set, 3D score availability, and any custom properties. We simultaneously audit the destination Nutshell account for existing custom fields, user list, pipeline structure, and lead/person configuration preference. The discovery output is a written migration scope and an export file specification shared with the Right On Interactive team.
Schema design and custom field provisioning
We provision custom fields in Nutshell before any data import. This includes a lifecycle_stage__c picklist field with values matching the Right On Interactive stage label set, three custom number fields for the 3D score sub-dimensions (roi_behavioral_score__c, roi_demographic_score__c, roi_firmographic_score__c), and any campaign or program metadata fields needed for engagement mapping. Custom fields are deployed into Nutshell's account settings before the first import batch. We also confirm whether the customer prefers a Lead-based or Person-based model for unqualified prospects.
Export file validation and sample import
We receive the exported file from Right On Interactive and validate it against the migration schema. We run a sample import of up to 100 records into Nutshell's sandbox or staging environment to confirm field mapping, custom field population, and record linkage (Person to Account, Activity to Person). The customer's Nutshell admin reviews the sample import results and flags any corrections before the full migration proceeds.
Account and User provisioning
We extract every distinct owner referenced in the Right On Interactive export and match by email against the Nutshell destination's user list. Any owner without a matching Nutshell user is flagged in a reconciliation queue for the customer's admin to provision before record import resumes. Account records (from Right On Interactive Companies) are imported first so that AccountId references are resolved at Person insert time.
Full production migration in dependency order
We run production migration in record-dependency order: Accounts (from Right On Interactive Companies), Persons (with AccountId resolved and lifecycle stage mapped), Leads (for unqualified prospects, with the lifecycle stage split applied), Activities (email opens, clicks, form submissions, event registrations via API batched requests with rate-limit handling), and custom score fields populated from the 3D scoring export. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and automation playbook delivery
We freeze writes on the Right On Interactive side during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver the automation playbook documenting each lifecycle-triggered workflow with its trigger conditions, filter logic, and recommended rebuild approach in the customer's chosen marketing automation layer. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team.
Platform deep dives
Right On Interactive
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
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 Right On Interactive and Nutshell.
Object compatibility
1 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
Right On Interactive: Not publicly documented.
Data volume sensitivity
Right On Interactive 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 Right On Interactive to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Right On Interactive 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 Right On Interactive
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.