CRM migration
Field-level mapping, validation, and rollback between Apptivo and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Apptivo
Source
Nutshell
Destination
Compatibility
10 of 12
objects map 1:1 between Apptivo and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Apptivo to Nutshell is a consolidation as much as a migration. Apptivo distributes CRM data across nine app groups, each with its own custom attribute layer; Nutshell uses a unified Contacts object with an optional People or Companies variant, which requires flattening the Apptivo multi-app schema into a single-object model. We extract Contacts and Leads from the Apptivo CRM app, map them to Nutshell's Contact structure, pull Customers from the Accounts app into Nutshell's Companies, and transfer Opportunities with pipeline stage names remapped to Nutshell's pipeline configuration. Engagement history (calls, emails, meetings, tasks, notes) migrates against the resolved Contact and Company parent records. Workflows, automations, and per-app custom attribute logic do not carry forward; we document every workflow and each custom attribute set so your admin has a rebuild checklist for the Nutshell side.
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 Apptivo 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.
Apptivo
Contact (CRM app)
Nutshell
Contact
1:1Apptivo Contacts from the CRM app map to Nutshell Contacts with standard fields (name, email, phone, address) transferred 1:1. We resolve any per-app custom attributes defined in the CRM app's Master Layout to Nutshell custom fields on Contact, using the attribute label as the field name. Multi-value custom attributes (dropdowns, checkboxes) map to Nutshell's equivalent picklist or multi-select fields. Email is used as the dedupe key during import.
Apptivo
Lead
Nutshell
Contact
1:manyApptivo Lead records merge into Nutshell's unified Contact object. The Apptivo Lead's lead_status, lead_score, and lifecycle_stage properties migrate as custom fields on the Nutshell Contact so that the customer's lead qualification history is preserved. If the same person exists as both an Apptivo Lead and an Apptivo Contact, we deduplicate by email and preserve both histories as activity records on the single Nutshell Contact.
Apptivo
Customer (Customers app)
Nutshell
Company
1:1Apptivo Customers from the Customers app map to Nutshell Companies. The company name, billing address, shipping address, and industry classification transfer directly. We link the Apptivo Customer's associated Contacts to the new Nutshell Company via the People field on the Company record. Any custom attributes in the Customers app's Master Layout map to Nutshell Company custom fields.
Apptivo
Opportunity
Nutshell
Opportunity
1:1Apptivo Opportunities map directly to Nutshell Opportunities. The opportunity name, amount, expected close date, and stage name transfer 1:1. We map Apptivo pipeline stage names to Nutshell pipeline stage values during import. The associated Contact and Customer links resolve via the email dedupe key and the Company name match respectively. Lost-won reasons from Apptivo custom fields migrate as a custom picklist field on the Nutshell Opportunity.
Apptivo
Engagement: Email (CRM app)
Nutshell
Contact Activity (Email)
1:1Apptivo email engagements on Contacts and Leads migrate as email activities on the corresponding Nutshell Contact record. Email subject, body, sender, and recipient transfer. The original timestamp is preserved on the activity so the Contact's timeline reflects the full history. We resolve the parent Contact by email match before inserting.
Apptivo
Engagement: Call (CRM app)
Nutshell
Contact Activity (Call)
1:1Apptivo call engagements migrate as call activities on the resolved Nutshell Contact. Call duration, disposition, and any notes transfer as custom fields on the activity record. Original timestamp and owner assignment carry forward. If the Apptivo call record includes a recording URL, we note it in the activity but do not migrate the binary attachment; the URL is preserved in a custom field for the admin to handle separately.
Apptivo
Engagement: Meeting (CRM app)
Nutshell
Contact Activity (Meeting)
1:1Apptivo meeting engagements migrate as meeting activities on the Nutshell Contact. Title, date, location, and attendee list transfer. Attendees without existing Contact records in Nutshell are created as new Contact records and linked to the meeting activity. Original timestamp is preserved for timeline ordering.
Apptivo
Engagement: Task (CRM app)
Nutshell
Contact Activity (Task)
1:1Apptivo task engagements on Contacts and Leads migrate as tasks on the resolved Nutshell Contact. Task subject, due date, status, and owner assignment transfer directly. The owner resolves via email match to a Nutshell User. Completed task notes from Apptivo transfer as the task description.
Apptivo
Engagement: Note (CRM app)
Nutshell
Contact Note
1:1Apptivo notes on Contacts and Leads migrate as notes attached to the resolved Nutshell Contact. Note body, author, and creation timestamp transfer. If the Apptivo note includes file attachments, the attachments are migrated separately as file links and associated to the same Nutshell Contact record.
Apptivo
Case (Helpdesk app)
Nutshell
Case
1:1Apptivo Cases from the Helpdesk app map to Nutshell Cases. Case status, priority, owner, subject, and description transfer. Conversation threads (customer and agent replies) migrate as email message records linked to the Case. The associated Customer record resolves to the Nutshell Company by name match. Custom fields from the Cases app Master Layout map to custom fields on the Nutshell Case object.
Apptivo
Custom Attributes (per app)
Nutshell
Custom Fields (per object)
lossyEach Apptivo app has its own Master Layout with independent custom attribute sets. During discovery, we enumerate all custom attributes across all active apps and build a per-app mapping table. Text, number, date, and dropdown custom attributes map to Nutshell custom fields on the corresponding object. Multi-select dropdowns map to Nutshell multi-select fields. Custom attributes that have no equivalent in Nutshell are flagged in the mapping table for the customer to decide whether to create a custom field or drop the data.
Apptivo
Workflow Rules
Nutshell
Workflow Rules (rebuild required)
1:1Apptivo workflow rules are configuration artifacts bound to app-specific object IDs and stage transitions. They do not export as data and have no equivalent in Nutshell's workflow model. We do not migrate workflow rules. We deliver a written inventory of every active workflow found in each Apptivo app during scoping, including its trigger, conditions, actions, and a recommended Nutshell workflow equivalent. The customer's admin rebuilds these in Nutshell's workflow builder post-migration. This is documented scope, not automated migration.
| Apptivo | Nutshell | Compatibility | |
|---|---|---|---|
| Contact (CRM app) | Contact1:1 | Fully supported | |
| Lead | Contact1:many | Fully supported | |
| Customer (Customers app) | Company1:1 | Fully supported | |
| Opportunity | Opportunity1:1 | Fully supported | |
| Engagement: Email (CRM app) | Contact Activity (Email)1:1 | Fully supported | |
| Engagement: Call (CRM app) | Contact Activity (Call)1:1 | Fully supported | |
| Engagement: Meeting (CRM app) | Contact Activity (Meeting)1:1 | Fully supported | |
| Engagement: Task (CRM app) | Contact Activity (Task)1:1 | Fully supported | |
| Engagement: Note (CRM app) | Contact Note1:1 | Fully supported | |
| Case (Helpdesk app) | Case1:1 | Fully supported | |
| Custom Attributes (per app) | Custom Fields (per object)lossy | Fully supported | |
| Workflow Rules | Workflow Rules (rebuild required)1: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.
Apptivo gotchas
Workflow automations are not exportable data
Per-app custom attributes create a hidden field-mapping burden
65K+ record export limit can split large datasets
IP whitelisting can block migration server IPs
Professional Implementation timelines rarely match actual deployment
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
Discovery and data audit
We audit every active Apptivo app with data: CRM (Contacts, Leads, Opportunities), Customers, Cases, and any other app storing relevant records. We enumerate per-app custom attributes from each app's Master Layout, count record volumes per object, and identify active workflow rules across all apps. We also verify IP whitelisting status on the Apptivo account. The discovery output is a written scope document with a per-app record count, a custom attribute inventory, and a workflow inventory.
Schema mapping and Nutshell configuration
We design the Nutshell destination schema before any data moves. This includes creating custom fields on Contact, Company, Opportunity, and Case to receive the per-app custom attributes from Apptivo. We configure the Nutshell pipeline stages to match the Apptivo opportunity pipeline stage names. We also set up the Nutshell workflow framework as a baseline for the post-migration rebuild. If the customer uses Nutshell's People-and-Companies variant, we confirm the data model preference during this step.
Staging migration and reconciliation
We run a full migration into a Nutshell staging environment using production-like data volumes. The customer reconciles record counts per object, spot-checks 20-30 records against the Apptivo source for field-level accuracy, and reviews the custom field data on a sample of records. Any mapping corrections, dropped fields, or schema adjustments happen in staging before production migration begins. This step prevents corrections in production, which are more disruptive.
Parent-record resolution and deduplication
We resolve all parent-record references before inserting child records. Apptivo Contacts link to Customers; we match each Contact's associated Customer to a Nutshell Company by name. Apptivo Cases link to Customers and Contacts; we resolve these references to Nutshell Company and Contact records. Email is used as the dedupe key across Contact and Lead objects to prevent duplicate records in Nutshell. Any unresolved references are held in a reconciliation queue for the customer's admin to resolve before the next migration phase.
Production migration in dependency order
We run production migration in record-dependency order: Companies (from Apptivo Customers), then Contacts (with Company lookup resolved), then Opportunities (with Contact and Company lookups resolved), then Cases (with Company and Contact lookups resolved), then engagement history (calls, emails, meetings, tasks, notes) against resolved parent Contact and Company records. Each phase emits a row-count reconciliation report before the next phase begins. Workflow rules are not migrated; we deliver the workflow inventory document at this step for the admin to begin rebuilding.
Cutover, delta sync, and workflow rebuild handoff
We freeze writes to Apptivo during the cutover window, run a final delta migration of any records created or modified during the migration window, then mark Nutshell as the system of record. We deliver the workflow inventory and custom attribute rebuild checklist to the customer's admin team. We support a three-day hypercare window where we resolve any reconciliation issues raised by the team. Workflow rebuilds, Nutshell automation configuration, and training are outside the standard migration scope and can be scoped as a separate engagement.
Platform deep dives
Apptivo
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 Apptivo 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
Apptivo: Not publicly documented — Apptivo's developer docs do not publish numeric rate limits. Typical SaaS throttling is assumed and confirmed by behavior during scoping..
Data volume sensitivity
Apptivo 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 Apptivo to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Apptivo 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 Apptivo
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.