CRM migration
Field-level mapping, validation, and rollback between Mazrica Sales (formerly Senses) and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Mazrica Sales (formerly Senses)
Source
Nutshell
Destination
Compatibility
6 of 8
objects map 1:1 between Mazrica Sales (formerly Senses) and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Moving from Mazrica Sales (formerly Senses) to Nutshell is a structural simplification for teams that have outgrown the feature depth and annual contract commitment of a Japan-focused SFA platform. Mazrica Sales uses a card-based Kanban pipeline, AI-driven deal scoring, and a multi-object schema with full API access to Contacts, Companies, Opportunities, Activities, Lifecycle Stages, and Custom Objects. Nutshell consolidates these into People (unified contact/prospect), Companies, Leads, Deals, and Activities with a simpler data model that does not support custom objects natively. We map the Senses API objects to their Nutshell equivalents, flag any Custom Object records that require manual recreation in Nutshell, and preserve the full activity timeline including timestamps and owner assignments. Workflows, automations, and the Senses Workato connector configuration do not migrate; we deliver a written inventory of these artifacts for the customer's admin to rebuild in Nutshell or an iPaaS 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 Mazrica Sales (formerly Senses) 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.
Mazrica Sales (formerly Senses)
Contact
Nutshell
Person
1:1Mazrica Sales Contact records map to Nutshell Person. We map name fields, email addresses, phone numbers, and address fields directly. The Mazrica Sales Lifecycle Stage property on Contact has no direct Nutshell equivalent, so we store it as a custom Person field (lifecycle_stage__c) for audit and reporting purposes. Owner assignment resolves by email match against Nutshell Users.
Mazrica Sales (formerly Senses)
Company
Nutshell
Company
1:1Mazrica Sales Company records map to Nutshell Company directly. Company name, website, industry, employee count, and annual revenue map to Nutshell's equivalent fields. We use the domain field as a deduplication key during import. Company records must exist before Contact import to satisfy the Person-to-Company relationship.
Mazrica Sales (formerly Senses)
Opportunity
Nutshell
Deal
1:1Mazrica Sales Opportunities (案件) map to Nutshell Deal. Stage name, amount, expected close date, owner assignment, and description migrate directly. Custom pipeline stages in Mazrica Sales require mapping to Nutshell Deal stages; we flag any stages that do not have a direct Nutshell equivalent and recommend stage name normalization during scoping.
Mazrica Sales (formerly Senses)
Activity
Nutshell
Activity
1:1Mazrica Sales Activities (行動) including calls, emails, meetings, and tasks map to Nutshell Activity records. Activity type, date, owner, related Person (via Contact lookup), related Deal (via Opportunity lookup), and notes content migrate. We preserve the full activity timeline ordering by setting the activity timestamp to the original Senses timestamp. Bulk activity migration uses batched API inserts with exponential backoff on rate limit responses.
Mazrica Sales (formerly Senses)
Custom Object
Nutshell
Custom Fields on Person/Company/Deal
lossyMazrica Sales Custom Objects have no native Nutshell equivalent. We work with the customer during scoping to identify which Custom Object fields are critical to preserve and map them to available custom fields on Person, Company, or Deal. Nutshell supports custom fields on its core objects, but the number of custom fields and the ability to create related-record structures is limited compared to Mazrica Sales Custom Objects. Low-priority Custom Objects are flagged for manual recreation or spreadsheet export post-migration.
Mazrica Sales (formerly Senses)
Lifecycle Stage
Nutshell
Custom Person Field
lossyThe Mazrica Sales LifecycleStageSetting API exposes configurable lifecycle stage values (e.g., 新規, 見込み, 提案中, 成約, 失注) that are stored as a property on Contact. Nutshell does not have a built-in lifecycle stage model. We map the existing stage values to a custom Person field (lifecycle_stage__c) and document the full stage list in the migration scope for the customer's admin to use in Nutshell filtering and reporting.
Mazrica Sales (formerly Senses)
User/Owner
Nutshell
User
1:1Mazrica Sales User records carrying roles and team assignments map to Nutshell Users. We resolve owners by email address match. Any Senses Owner without a matching Nutshell User email goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active/inactive status on the Nutshell User should match the Senses user's active status at migration time.
Mazrica Sales (formerly Senses)
Attachment
Nutshell
Not migrated
1:1Mazrica Sales file attachments associated with Contacts, Companies, or Opportunities are not exposed via the documented v1 REST API (senses-open-api.mazrica.com). We do not migrate binary attachments through the API path. We advise customers to use the Mazrica Sales web interface to manually export any attachments that must be preserved, and recommend a shared drive or document management system as the post-migration storage location.
| Mazrica Sales (formerly Senses) | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| Activity | Activity1:1 | Fully supported | |
| Custom Object | Custom Fields on Person/Company/Deallossy | Fully supported | |
| Lifecycle Stage | Custom Person Fieldlossy | Fully supported | |
| User/Owner | User1:1 | Fully supported | |
| Attachment | Not migrated1: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.
Mazrica Sales (formerly Senses) gotchas
Rebrand from Senses to Mazrica Sales creates API path ambiguity
Minimum 5-user contract requirement on Starter tier
Annual contract commitment with no free trial
AI features require historical data volume to function
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 scoping
We audit the source Mazrica Sales account via the v1 REST API (senses-open-api.mazrica.com) across object counts (Contacts, Companies, Opportunities, Activities, Custom Objects), pipeline and stage definitions, active user count, and any workflow or automation configurations. We identify Lifecycle Stage values and map them to the custom field strategy for Nutshell Person records. We confirm the current contract renewal date to establish the migration deadline and flag the 35-day cancellation notice requirement. The discovery output is a written migration scope with record counts, a preliminary object mapping, and a Nutshell plan recommendation based on team size and feature requirements.
Schema design and custom field planning
We design the Nutshell destination schema during this phase. This includes identifying which Custom Object fields map to Nutshell custom fields on Person, Company, or Deal, confirming the custom field limit per Nutshell plan, and designing the lifecycle_stage__c custom field on Person. We document any Custom Object records that cannot be represented in Nutshell's schema and recommend a manual export approach. We also confirm the owner email mapping between Senses Users and Nutshell Users, and identify any owner records that require provisioning before migration.
Proof-of-migration validation
We run a full migration into a Nutshell trial account using production-like data volume. The customer's team lead reconciles record counts across all objects (Persons in, Companies in, Deals in, Activities in), spot-checks 20-30 records for field-level accuracy including Japanese-character rendering, and verifies that the Person-to-Company relationship links are correct. Any mapping corrections, encoding issues, or field type mismatches surface here before production migration begins.
Production migration in dependency order
We run production migration in record-dependency order: Companies (from Mazrica Sales Companies), Persons (from Contacts with CompanyId resolved and lifecycle_stage__c populated), Deals (from Opportunities with OwnerId resolved via email match and stage mapped), Activities (calls, emails, meetings, tasks in timestamp order via batched API inserts). Custom Object data is migrated last with its field mapping documented. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, final delta, and workflow inventory delivery
We freeze writes to Mazrica Sales 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 and workflow inventory document to the customer's admin team with recommendations for Nutshell native automation or Zapier/Make alternatives. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. We do not rebuild Mazrica Sales workflows in Nutshell as part of the migration scope.
Platform deep dives
Mazrica Sales (formerly Senses)
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 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 Mazrica Sales (formerly Senses) and Nutshell.
Object compatibility
3 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
Mazrica Sales (formerly Senses): Not publicly documented.
Data volume sensitivity
Mazrica Sales (formerly Senses) exposes a bulk API — large-volume migrations stream efficiently.
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 Mazrica Sales (formerly Senses) to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Mazrica Sales (formerly Senses) 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 Mazrica Sales (formerly Senses)
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.