CRM migration
Field-level mapping, validation, and rollback between Mazrica Sales (formerly Senses) and Zoho CRM. We move data and schema; workflows are rebuilt natively in Zoho CRM.
Mazrica Sales (formerly Senses)
Source
Zoho CRM
Destination
Compatibility
7 of 10
objects map 1:1 between Mazrica Sales (formerly Senses) and Zoho CRM.
Complexity
BStandard
Timeline
4-6 weeks
Overview
Moving from Mazrica Sales (formerly Senses) to Zoho CRM is a structural migration that crosses a language and ecosystem boundary. Mazrica Sales stores lifecycle stages as a Contact property and uses a Kanban card pipeline for Opportunities; Zoho CRM uses a Leads module for unqualified prospects and a Deals module (or Opportunities with a configuration toggle) for qualified pipeline. We map the Mazrica lifecycle stage values into Zoho Leads or Contacts depending on stage, configure Zoho's pipeline stages to match the named stages exported from Mazrica, and preserve activity history (calls, emails, meetings, tasks) through Zoho's REST API with chunking and parent-record lookup resolution. The 2023 Senses-to-Mazrica rebrand means the API base URL still reads senses-open-api.mazrica.com; we validate endpoint paths explicitly during scoping. Workflows, Sequences, custom automations, and saved reports do not migrate. We deliver a written inventory of every automation artifact requiring rebuild in Zoho.
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 Zoho CRM, 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
Zoho CRM
Lead or Contact
1:manyMazrica Sales Contacts with Lifecycle Stage values of 新規 (New), リード (Lead), or 興味本位 (Marketing Qualified) map to Zoho CRM Lead. Lifecycle Stage values of 提案中 (Proposal), 交渉中 (Negotiation), 受注 (Customer Won), or 失注 (Customer Lost) map to Zoho CRM Contact. We compute the split using the lifecycle_stage field during migration, and preserve the original Mazrica Lifecycle Stage in a custom Zoho field mzrica_lifecycle_stage__c on both Lead and Contact for audit and reporting. Mazrica Contacts without a lifecycle stage value are flagged for manual assignment before import.
Mazrica Sales (formerly Senses)
Company
Zoho CRM
Account
1:1Mazrica Sales Company records map directly to Zoho CRM Account. The Company name becomes Account Name; the domain field maps to Account Website. Company ID from Mazrica is stored in a custom field mzrica_company_id__c on the Account as a dedupe and cross-reference key. Account is created before any Contact import so that the Account-Contact lookup is satisfied at insert time.
Mazrica Sales (formerly Senses)
Opportunity
Zoho CRM
Deals (or Opportunities in Classic mode)
1:1Mazrica Sales Opportunities (案件) map to Zoho CRM Deals in the Deals pipeline view (or Opportunities in CRM Classic mode). The Mazrica deal stage name maps to the Zoho Stage field. Pipeline name from Mazrica maps to Zoho Pipeline Name. Deal amount, expected close date, and owner assignment migrate directly. Closed-won and closed-lost reasons from Mazrica custom fields become Zoho Deal custom fields.
Mazrica Sales (formerly Senses)
Deal Stage
Zoho CRM
Deal Stage
lossyEach Mazrica Sales pipeline stage becomes a Zoho Deal Stage within the configured pipeline. We create the pipeline and stage names in Zoho Setup before migration so that the stage dropdown values are whitelisted and match the incoming Mazrica stage names exactly. Probability percentages from Mazrica map to Zoho Stage Probability. If Mazrica uses custom pipeline stages, we create matching Zoho pipeline views rather than collapsing them into a default pipeline.
Mazrica Sales (formerly Senses)
Activity: Calls, Emails, Meetings, Tasks
Zoho CRM
Tasks, Events, Calls, Notes
1:1Mazrica Sales Activity records (行動) map to Zoho CRM Tasks (calls, emails, tasks) and Events (meetings). The activity type field determines the Zoho target object. Activity timestamps (created_at, updated_at) are preserved as custom date fields in Zoho since the Zoho Created Time field is set at import time and cannot be backdated through the API. Owner assignment resolves by email match to Zoho Users. Activity records without a valid owner match go to a reconciliation queue for admin provisioning before the activity import phase.
Mazrica Sales (formerly Senses)
Lifecycle Stage Setting
Zoho CRM
Lead Status and Contact Status picklists
lossyMazrica Sales LifecycleStageSetting API exposes the configured stage names and their order. We map each named stage to a Zoho Lead Status value (for stages mapped to Lead) or a custom Contact Status picklist (for stages mapped to Contact). If the customer uses non-standard Japanese stage names, we configure them as custom picklist values in Zoho rather than substituting English defaults.
Mazrica Sales (formerly Senses)
User/Owner
Zoho CRM
User
1:1Mazrica Sales User records carrying role and team assignments map to Zoho CRM User records. We resolve owners by email address match. Any Mazrica User without a matching Zoho User email goes to a reconciliation queue. The customer provisions missing Zoho Users before the record import phases resume because OwnerId references are required on Accounts, Contacts, and Deals.
Mazrica Sales (formerly Senses)
Custom Object
Zoho CRM
Custom Module
1:1Mazrica Sales CustomObjectSetting and CustomObjects API records map to Zoho CRM Custom Modules. We pre-create the destination module schema in Zoho Setup with matching field types before any data import. Lookup relationships between Mazrica custom objects resolve at migration time by querying the destination object for the related record by external ID (stored in a custom field on each record). Custom module imports run last because they often have lookups to Contacts, Accounts, or Deals.
Mazrica Sales (formerly Senses)
Attachments
Zoho CRM
Not migrated via API
1:1File attachments associated with Mazrica Sales Contacts 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 Mazrica Sales's built-in export function to download attachments separately before migration and re-upload manually in Zoho CRM post-migration. Zoho's Files API can receive these uploads if the customer prefers programmatic re-upload.
Mazrica Sales (formerly Senses)
Reports and Dashboards
Zoho CRM
Not migrated
1:1Saved reports and dashboard configurations are not accessible via the Mazrica Sales public API. We do not migrate analytics artifacts. We deliver a written map of every named Mazrica Sales report and its closest Zoho CRM Analytics equivalent (Zoho Analytics, Custom Report Builder, or standard module reports). The customer's Zoho admin rebuilds reports post-migration based on this inventory.
| Mazrica Sales (formerly Senses) | Zoho CRM | Compatibility | |
|---|---|---|---|
| Contact | Lead or Contact1:many | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Opportunity | Deals (or Opportunities in Classic mode)1:1 | Fully supported | |
| Deal Stage | Deal Stagelossy | Fully supported | |
| Activity: Calls, Emails, Meetings, Tasks | Tasks, Events, Calls, Notes1:1 | Fully supported | |
| Lifecycle Stage Setting | Lead Status and Contact Status picklistslossy | Fully supported | |
| User/Owner | User1:1 | Fully supported | |
| Custom Object | Custom Module1:1 | Fully supported | |
| Attachments | Not migrated via API1:1 | Not supported | |
| Reports and Dashboards | 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
Zoho CRM gotchas
API access requires Professional tier or above
Subform fields do not export cleanly via CSV
API credit consumption is non-linear
Export download links expire in 7 days
Owner (User) assignments require pre-mapped user IDs
Pair-specific challenges
Migration approach
Discovery and API path validation
We audit the source Mazrica Sales portal across all tiers: contact volume, company volume, opportunity count and pipeline names, activity record count by type, lifecycle stage configuration, custom object schemas, and active user count. We validate the senses-open-api.mazrica.com endpoints and confirm authentication (API key format and scopes) before extraction begins. We also confirm whether the destination Zoho CRM org is in Deals mode (pipeline Kanban view) or CRM Classic mode (Opportunity record types) because this determines the destination object for the opportunity migration phase. The discovery output is a written migration scope document with record counts per object and a Zoho edition recommendation based on custom module and user count requirements.
Schema design and lifecycle stage mapping
We design the destination schema in Zoho CRM Setup. This includes creating or mapping Mazrica Sales pipeline stages to Zoho Deal Stages within a configured pipeline, provisioning custom modules for Mazrica Sales Custom Objects with matching field types and lookup relationships, creating the mzrica_lifecycle_stage__c custom field on Lead and Contact, and configuring Lead Status and Contact Status picklist values to match the named Mazrica lifecycle stages exported from the LifecycleStageSetting API. The customer reviews and approves the lifecycle stage mapping table before the split phase runs. Schema is deployed into a Zoho Sandbox or staging org first for validation.
Sandbox migration and reconciliation
We run a full migration into a Zoho staging org using production-equivalent data volume. The customer's Zoho admin reconciles record counts (Accounts from Companies, Contacts and Leads from Contacts with the lifecycle split applied, Deals from Opportunities, Activities per type), spot-checks 25-50 records against the Mazrica Sales source, and validates the lifecycle stage mapping output. Any field type mismatches, missing picklist values, or validation rule blocks surface here. The customer signs off the staging migration before production migration begins.
Owner reconciliation and User provisioning
We extract every distinct Mazrica Sales User referenced on Contact, Company, Opportunity, and Activity records and match by email address against the Zoho destination org's User table. Users without a matching Zoho User go to a reconciliation queue with the owning record count for each missing user. The customer's Zoho admin provisions any missing Users (active or inactive depending on whether the original Mazrica user is still employed). Owner resolution must complete before the record import phases because OwnerId is a required reference on Accounts, Contacts, and Deals in Zoho.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Mazrica Companies), Leads and Contacts (with the lifecycle stage split applied and mzrica_lifecycle_stage__c populated), Deals (with AccountId and OwnerId resolved), Activities (Tasks, Events, Calls via Zoho CRM REST API with chunking and rate-limit pacing), Custom Modules (last because they often have lookups to Contacts, Accounts, or Deals). Each phase emits a row-count reconciliation report before the next phase begins. We preserve Mazrica created_at timestamps as custom date fields because Zoho's native created date is set at import time.
Cutover, validation, and automation inventory handoff
We freeze Mazrica Sales write access during cutover, run a final delta migration of any records modified during the migration window, then enable Zoho CRM as the system of record. We deliver the automation inventory document listing every Mazrica Sales workflow, sequence, and automation artifact that requires rebuild in Zoho (Workflows, Approval Rules, Blueprint configurations, and any Scheduled Functions). We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's sales team. We do not rebuild automations in Zoho as part of the standard migration scope; that work is a separate engagement for the customer's Zoho admin or a Zoho implementation partner.
Platform deep dives
Mazrica Sales (formerly Senses)
Source
Strengths
Weaknesses
Zoho CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 Zoho CRM.
Object compatibility
2 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 Zoho CRM migration scoping. Not seeing yours? Book a call.
Walk through your Mazrica Sales (formerly Senses) to Zoho CRM 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 Zoho CRM
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.