CRM migration
Field-level mapping, validation, and rollback between SuperOffice CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
SuperOffice CRM
Source
Nutshell
Destination
Compatibility
7 of 10
objects map 1:1 between SuperOffice CRM and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Moving from SuperOffice CRM to Nutshell is primarily a geographic and pricing simplification. SuperOffice's EU-hosted infrastructure, unified sales-marketing-service model, and ERP integrations serve European mid-market companies with compliance requirements. Nutshell's US-hosted platform, transparent per-user pricing (Foundation $16 to Enterprise $67 per user per month), and included migration assistance target US and international SMBs that prioritize cost predictability and ease of use over deep ERP connectivity. We map SuperOffice Contacts and Companies to Nutshell People and Organizations, Deals to Nutshell Deals, and Activities to Tasks. Quote Alternatives (SuperOffice's multi-version proposal structure) flatten to a primary quote with secondary alternatives stored as JSON in a custom field. Selections (SuperOffice's named dynamic lists) export as tagged records without a native equivalent in Nutshell. We do not migrate SuperOffice Workflows, Project automations, or ERP sync rules; these are documented for the customer admin to rebuild or reconfigure post-migration.
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 SuperOffice CRM 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.
SuperOffice CRM
Contact
Nutshell
Person
1:1SuperOffice Contact records map directly to Nutshell Person. Name, email, phone, address, and custom properties transfer cleanly. We preserve the Contact-Company link by resolving the associated Company record ID before inserting the Person, then setting the organization_id on Person to the mapped Nutshell Organization.
SuperOffice CRM
Company
Nutshell
Organization
1:1SuperOffice Company maps to Nutshell Organization. The company name, domain, address, and industry fields migrate. Organization is inserted before Person records so that the organization relationship is satisfied at Person import time.
SuperOffice CRM
Sale (Deal)
Nutshell
Deal
1:1SuperOffice Sale maps to Nutshell Deal. Deal name, amount, stage, expected close date, and sale type transfer. The SuperOffice SaleType list value becomes a Nutshell custom field sale_type__c because Nutshell Deal does not have a native sale type property. Owner assignment migrates by email match to Nutshell User.
SuperOffice CRM
Activity (Call, Task, Appointment)
Nutshell
Task
1:1SuperOffice Activities (calls, tasks, appointments) map to Nutshell Task records. Activity type, duration, completion status, and timestamp preserve. We set Task type and subtask fields to reflect the original SuperOffice activity category. The activity-to-record link (Contact, Company, Sale) migrates by resolving external IDs to the mapped Nutshell record IDs.
SuperOffice CRM
Quote
Nutshell
Quote (Nutshell built-in)
1:1SuperOffice Quote maps to Nutshell Quote attached to a Deal. The primary QuoteAlternative becomes the Nutshell quote with its line items. Discount and earning values at the Alternative level transfer to Nutshell quote line item fields.
SuperOffice CRM
QuoteAlternative
Nutshell
Custom field on Quote (JSON)
lossySuperOffice Quote Alternatives (secondary proposal versions) have no native Nutshell equivalent because Nutshell Quote supports a single proposal version per Deal. We serialize secondary QuoteAlternatives as a JSON blob stored in a Nutshell custom field quote_alternatives__c. The full QuoteAlternative structure (line items, totals, valid until) is preserved in the JSON for admin reference post-migration.
SuperOffice CRM
Selection
Nutshell
Tags + saved filter documentation
lossySuperOffice Selections are named dynamic lists of Contacts, Companies, or Sales with membership rules. Nutshell has no dynamic list equivalent. We export Selection membership as tag values on the relevant records (e.g., tag: Selection_AnnualReview) and deliver a written inventory of each Selection's name, type, and member count so the customer admin can recreate static lists or Saved Filters in Nutshell.
SuperOffice CRM
Project
Nutshell
Custom field or Deal link
lossySuperOffice Project has no direct Nutshell equivalent. For migrations where Projects track deal-related milestones, we attach Project data as custom fields on the linked Nutshell Deal (project_name__c, project_status__c, project_type__c). For standalone Projects, we export them as a separate CSV inventory document for the admin to assess whether Nutshell's Tasks or a project management tool is the appropriate replacement.
SuperOffice CRM
User
Nutshell
User
1:1SuperOffice Users map to Nutshell Users by email address match. We extract active users and license status from SuperOffice. Any user without a matching Nutshell User record goes to a reconciliation queue for the admin to provision before record import. Role structures (SuperOffice's module-level access) do not migrate as Nutshell's permission model is simpler and permission-set-based.
SuperOffice CRM
Tag
Nutshell
Tag
1:1SuperOffice tags applied across Contact, Company, Sale, and Project objects migrate as Nutshell tags on the corresponding Person, Organization, Deal, or Task record. Tag normalization handles any differences in case and spacing before insert.
| SuperOffice CRM | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company | Organization1:1 | Fully supported | |
| Sale (Deal) | Deal1:1 | Fully supported | |
| Activity (Call, Task, Appointment) | Task1:1 | Fully supported | |
| Quote | Quote (Nutshell built-in)1:1 | Fully supported | |
| QuoteAlternative | Custom field on Quote (JSON)lossy | Fully supported | |
| Selection | Tags + saved filter documentationlossy | Fully supported | |
| Project | Custom field or Deal linklossy | Fully supported | |
| User | User1:1 | Fully supported | |
| Tag | Tag1: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.
SuperOffice CRM gotchas
On-prem to cloud migration requires SuperOffice 7.1 minimum
Customizations and integrations may break after on-prem to cloud migration
Duplicate email addresses block user migration
Quote-Alternative hierarchy flattens in most destination CRMs
Activity-to-record associations require post-migration verification
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 version audit
We audit the source SuperOffice installation for version (on-prem vs online, version number), user count, custom field inventory (userDefined table), custom table count, active integrations, and Quote Alternative usage. We also assess Nutshell's current state (trial or existing account) and confirm which Nutshell plan the customer has selected. The discovery output is a written migration scope with object mapping, data quality issues, and an estimated timeline.
Data quality remediation
We run duplicate-email scans on SuperOffice Users, check for SODictionarySDK artifacts in the database, flag incomplete Contact records missing required fields (email, name), and identify Quote Alternatives that require JSON serialization. We deliver a data quality report to the customer with remediation steps. Dirty data that is not remediated before migration imports dirty into Nutshell and inflates the post-migration cleanup burden.
Schema mapping and Nutshell custom field creation
We design the field mapping between SuperOffice objects and Nutshell equivalents, including any custom fields required for Quote Alternatives, sale types, and project data. Custom fields are pre-created in Nutshell (as custom properties on Person, Organization, Deal, or Quote) before any data import. We validate the mapping in a Nutshell test environment using a small sample before full migration.
Sample migration and reconciliation
We run a sample migration of 50-100 records per object type into the Nutshell production account. The customer reconciles a random sample of records against the SuperOffice source, confirms that tag normalization, activity linking, and quote mapping are correct, and signs off before the full migration begins. Mapping corrections happen in this phase, not in production.
Full migration in dependency order
We run production migration in record-dependency order: Organizations first (from SuperOffice Companies), then Persons (with organization_id resolved), Deals (with Person and Organization links resolved), Quotes (with Deal link resolved), Activities (Tasks with Person and Deal links resolved via external ID resolution), Tags (applied to the migrated records). Quote Alternatives serialize to JSON and attach to the primary quote record.
Cutover, delta sync, and handoff documentation
We freeze SuperOffice writes during cutover, run a final delta migration of records modified during the migration window, then enable Nutshell as the system of record. We deliver the Selection inventory document (names, types, member counts) and the Quote Alternative JSON field documentation for the admin to process. We do not rebuild SuperOffice Workflows, Project automations, or ERP integrations in Nutshell; those are separate configuration tasks outside migration scope.
Platform deep dives
SuperOffice CRM
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 SuperOffice CRM 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
SuperOffice CRM: Tiered: Starter 500 req/min, Professional 2,500 req/min, Enterprise 10,000 req/min.
Data volume sensitivity
SuperOffice CRM 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 SuperOffice CRM to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your SuperOffice CRM 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 SuperOffice CRM
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.