CRM migration
Field-level mapping, validation, and rollback between TOTUS Marketing and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
TOTUS Marketing
Source
Nutshell
Destination
Compatibility
6 of 8
objects map 1:1 between TOTUS Marketing and Nutshell.
Complexity
CModerate
Timeline
2-4 weeks
Overview
Moving from TOTUS Marketing to Nutshell requires navigating an undocumented source schema. TOTUS Marketing operates as a proprietary system with no publicly available API documentation, object model, or field reference, which means every migration begins with direct API exploration rather than pre-built field mappings. We probe the source instance to identify which objects are present (Contacts, Accounts, Deals, custom fields), resolve owner and pipeline references, and then map to Nutshell's standard CRM schema: People, Organizations, Deals, Pipelines, and Activities. Engagements such as calls, emails, and meetings transfer as Activity records attached to the correct Person or Organization. We flag any TOTUS-specific proprietary objects that have no native Nutshell equivalent and document them for manual handling. Workflows, automation rules, and any marketing cadence features in TOTUS Marketing do not migrate; we deliver a written map of these for your team to rebuild inside Nutshell's automation builder.
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 TOTUS Marketing 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.
TOTUS Marketing
Contact / Person record
Nutshell
Person
1:1TOTUS Marketing Person records (discovered via API) map to Nutshell Person. The API exploration phase determines whether names, emails, phone numbers, addresses, and any custom fields exist as top-level attributes. We map each discovered attribute to the equivalent Nutshell Person field by type (string, email, phone, date, picklist). Any TOTUS-specific custom fields are flagged as custom fields to create in Nutshell before import.
TOTUS Marketing
Company / Organization record
Nutshell
Organization
1:1TOTUS Marketing organization records map to Nutshell Organization. We resolve the domain or name field as the dedupe key. The Organization must import before any Person records that reference it, so we enforce this ordering in the migration pipeline. Owner assignment on the TOTUS side resolves to the corresponding Nutshell User by email match.
TOTUS Marketing
Deal / Opportunity record
Nutshell
Deal
1:1TOTUS Marketing Deal records map to Nutshell Deal. We discover the deal stage values, associated pipeline, amount fields, close dates, and owner references during the API exploration phase. The stage values map to Nutshell Pipeline stages that we configure before migration. Any custom deal fields discovered in TOTUS (discount percentages, renewal dates, product lines) are flagged for custom field creation in Nutshell.
TOTUS Marketing
Pipeline and stage configuration
Nutshell
Pipeline and stage configuration
lossyTOTUS Marketing pipeline structures (one or more pipelines, stage names, stage ordering) are discovered during the API exploration phase. We configure Nutshell Pipelines with stages matching the source names and order. Probability percentages from TOTUS map to Nutshell stage probabilities if present in the source data.
TOTUS Marketing
Owner / User
Nutshell
User
1:1TOTUS Marketing owner references on Contacts, Companies, and Deals resolve to Nutshell Users by email address match. Any TOTUS Owner without a matching Nutshell User goes to a reconciliation queue for the customer to provision the user before record import resumes. Active versus inactive status carries over if present in the TOTUS API response.
TOTUS Marketing
Activity / Engagement record
Nutshell
Activity (Task, Event, Email)
1:1If TOTUS Marketing exposes an activity or engagement API (calls, emails, meetings, notes), we map each record type to the corresponding Nutshell Activity object. Call records map to Task with type set to Call; meeting records map to Event with start and end time preserved; emails map to Task or a linked email record depending on what the TOTUS API exposes. The parent reference (Person or Organization) resolves at migration time. If the TOTUS API does not expose activity history, we document this limitation and note it in the migration handoff.
TOTUS Marketing
Note
Nutshell
Note
1:1TOTUS Marketing Note records map to Nutshell Note attached to the parent Person or Organization. The note body text and any associated metadata (author, timestamp) migrate as-is. Attachments referenced in notes require a separate discovery phase to determine whether they are stored as blobs in TOTUS or as linked file references.
TOTUS Marketing
Custom field (dynamic, per-instance)
Nutshell
Custom field (per-object)
lossyTOTUS Marketing custom fields vary by instance and are discovered during API exploration. We map each custom field to a Nutshell custom field on the equivalent object (Person, Organization, or Deal). Field types are inferred from the API response data type (string, integer, date, boolean, picklist). We create the Nutshell custom fields before the migration phase begins and update the mapping document with the final field pairings.
| TOTUS Marketing | Nutshell | Compatibility | |
|---|---|---|---|
| Contact / Person record | Person1:1 | Fully supported | |
| Company / Organization record | Organization1:1 | Fully supported | |
| Deal / Opportunity record | Deal1:1 | Fully supported | |
| Pipeline and stage configuration | Pipeline and stage configurationlossy | Fully supported | |
| Owner / User | User1:1 | Fully supported | |
| Activity / Engagement record | Activity (Task, Event, Email)1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Custom field (dynamic, per-instance) | Custom field (per-object)lossy | 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.
TOTUS Marketing gotchas
Catalog website points to wrong product
Distributed marketing template hierarchy is the complex piece
API access exists but is not deeply documented publicly
Limited public review base for benchmarking
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
API discovery and schema mapping
We connect to the customer's TOTUS Marketing instance via API (using credentials provided during onboarding) and systematically probe available endpoints. We enumerate object types, attribute names, data types, relationships, and any pagination or filtering parameters. We generate a TOTUS schema document that lists every discovered object, field, and relationship. This document is the source of truth for all downstream mapping work.
Nutshell schema preparation
We create the Nutshell custom fields discovered in the TOTUS schema that do not map to standard Nutshell fields. We configure Pipelines and stage values to match the TOTUS pipeline structure. We verify that the migration user has the required Nutshell API permissions and that any required integrations (Google Workspace, Microsoft 365) are connected. The Nutshell schema preparation output is a confirmed field mapping document signed off by the customer before any data moves.
Sample migration and reconciliation
We run a sample migration of up to 100 random records from each TOTUS object type into the corresponding Nutshell objects. The customer reviews the migrated sample data in Nutshell and confirms field mappings. Any field mapping corrections (wrong field, missing field, type mismatch) are documented and applied to the full migration configuration. Sample migration must be approved before the full migration proceeds.
Owner and user reconciliation
We extract every distinct TOTUS owner reference across Contacts, Companies, and Deals and match them against the Nutshell destination account's User list by email. Owners without a matching Nutshell User go to a reconciliation queue. The customer provisions any missing users in Nutshell before record migration resumes. OwnerId references are required on most standard objects and must resolve before bulk import.
Full production migration
We run production migration in dependency order: custom fields (created first), then Organizations, then People (with OrganizationId resolved), then Deals (with OwnerId and OrganizationId resolved), then Activity history. Each phase emits a row-count reconciliation report. We use Nutshell's API with batch chunking and exponential backoff to handle rate limits. Any records that fail validation (required field missing, invalid format) are held in an error queue and reported for manual resolution.
Cutover, validation, and handoff
We freeze TOTUS Marketing writes during cutover and run a final delta migration of any records modified during the migration window. We deliver a written inventory of any TOTUS objects, custom fields, or engagement records that could not map to Nutshell, with record counts and a data dictionary. We deliver a written inventory of any TOTUS automation or workflow-like features discovered during API exploration for the customer's admin to rebuild in Nutshell. We support a one-week hypercare window for reconciliation issues raised during the first week of Nutshell usage.
Platform deep dives
TOTUS Marketing
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 1 of 8 objects need a manual workaround.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across TOTUS Marketing and Nutshell.
Object compatibility
1 of 8 objects need a manual workaround.
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
TOTUS Marketing: Not publicly documented — typical SaaS limits assumed and confirmed during scoping..
Data volume sensitivity
TOTUS Marketing 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 TOTUS Marketing to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your TOTUS Marketing 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 TOTUS Marketing
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.