CRM migration

Migrate from Mazrica Sales (formerly Senses) to Nutshell

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) logo

Mazrica Sales (formerly Senses)

Source

Nutshell

Destination

Nutshell logo

Compatibility

75%

6 of 8

objects map 1:1 between Mazrica Sales (formerly Senses) and Nutshell.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Mazrica Sales (formerly Senses) logo

Mazrica Sales (formerly Senses)

What's pushing teams away

  • Feature breadth creates a steep learning curve — G2 reviewers note that having all capabilities available can make the tool feel complex to navigate for some users.
  • Pricing at higher tiers (Growth at ¥110,000/month, Enterprise at ¥330,000/month) scales into significant annual commitments with no published free trial to validate fit before paying.
  • AI order forecasting and risk analysis features require substantial historical deal data to produce useful outputs — teams with limited CRM history report underwhelming AI recommendations initially.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Mazrica Sales (formerly Senses) objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

Mazrica 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

maps to

Nutshell

Company

1:1
Fully supported

Mazrica 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

maps to

Nutshell

Deal

1:1
Fully supported

Mazrica 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

maps to

Nutshell

Activity

1:1
Fully supported

Mazrica 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

maps to

Nutshell

Custom Fields on Person/Company/Deal

lossy
Fully supported

Mazrica 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

maps to

Nutshell

Custom Person Field

lossy
Fully supported

The 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

maps to

Nutshell

User

1:1
Fully supported

Mazrica 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

maps to

Nutshell

Not migrated

1:1
Fully supported

Mazrica 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.

Gotchas + challenges

What specifically takes care here

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) logo

Mazrica Sales (formerly Senses) gotchas

Medium

Rebrand from Senses to Mazrica Sales creates API path ambiguity

Medium

Minimum 5-user contract requirement on Starter tier

Medium

Annual contract commitment with no free trial

Low

AI features require historical data volume to function

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Custom Objects require manual reconstruction in Nutshell

    Mazrica Sales Custom Objects are first-class API-accessible records with their own schema definitions, relationships, and bulk endpoints. Nutshell does not have a native Custom Object equivalent; custom fields are limited to the four core objects (Person, Company, Deal, Activity) with a flat field structure. If the customer's Mazrica Sales implementation uses Custom Objects for business-critical data (e.g., 製品, プロジェクト, 契約), we identify every Custom Object schema during scoping, map critical fields to available custom fields on Person/Company/Deal, and flag records that cannot be represented without a separate tool or spreadsheet. This work adds scope to both migration design and post-migration admin effort.

  • Japanese-language field values require encoding verification

    Mazrica Sales is a native Japanese-language product and many field values (contact names, company names, stage labels, activity notes) contain double-byte characters. The Senses API returns these as UTF-8 encoded JSON. We validate UTF-8 round-trip encoding during the proof-of-migration phase and verify that Japanese characters render correctly in Nutshell's interface after insert. Post-migration reconciliation should include a spot-check of 20-30 records containing Japanese text to confirm no encoding degradation occurred during the ETL process.

  • Workflows and automations do not migrate to Nutshell

    Mazrica Sales workflow rules and automation triggers (configured in the Growth and Enterprise tiers) have no direct Nutshell equivalent. Nutshell offers basic automation capabilities that differ structurally from Senses workflow definitions. We do not migrate automations as code. We deliver a written inventory of every active Mazrica Sales workflow with its trigger conditions, actions, and a recommendation for the equivalent Nutshell configuration or Zapier/Make workflow. The customer's admin rebuilds these post-migration as a separate task.

  • Annual contract cancellation requires 35-day notice window

    Mazrica Sales subscription cancellations and user reductions are only permitted at the contract renewal date and require application 35 days before the renewal date per the SaaSplats product listing terms. Teams planning a mid-contract migration must coordinate the cutover with the renewal window or negotiate an early termination. We flag the current contract end date and renewal deadline during scoping so the migration timeline accounts for the notice period and avoids paying for both platforms simultaneously beyond the minimum necessary overlap.

Migration approach

Six steps for a successful Mazrica Sales (formerly Senses) to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Mazrica Sales (formerly Senses) logo

Mazrica Sales (formerly Senses)

Source

Strengths

  • AI-assisted deal scoring, risk analysis, and order forecasting built directly into the opportunity workflow.
  • Card-based pipeline UI with drag-and-drop stage changes that reduces friction for sales reps on the move.
  • OCR名片 scanning and AI-powered deduplication for rapid contact creation from field encounters.
  • Native Japanese-language product and support team — no localization gap for domestic SMBs.
  • Workato pre-built connector and iPaaS support for teams with existing Japanese cloud toolchains.

Weaknesses

  • Feature-rich interface creates a learning curve — G2 reviewers note complexity for some user segments.
  • Minimum 5-user contract on Starter tier may be costly for very small sales teams.
  • No published free trial or free tier to evaluate the product before committing to an annual contract.
  • AI features require accumulated historical deal data to produce meaningful outputs — limited value at initial deployment.
  • Binary attachments and saved reports are not accessible via the public API.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 3 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Mazrica Sales (formerly Senses) and Nutshell.

  • Object compatibility

    B

    3 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Mazrica Sales (formerly Senses): Not publicly documented.

  • Data volume sensitivity

    A

    Mazrica Sales (formerly Senses) exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Mazrica Sales (formerly Senses) to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Mazrica Sales (formerly Senses) to Nutshell data migrations

Answers to the questions buyers ask most during Mazrica Sales (formerly Senses) to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between two and four weeks for accounts under 10,000 Contacts and 2,000 Deals with no Custom Objects. Migrations with Custom Objects that require field remapping, large engagement histories (over 100,000 activity records), or Japanese-language field verification requirements move to five to eight weeks. The 35-day contract cancellation notice window may extend the overall timeline if the customer coordinates cutover with the renewal date.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Mazrica Sales (formerly Senses).
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day