Migrate your Mazrica Sales (formerly Senses) data
Japan-born sales-first CRM and SFA with AI-driven deal scoring and a card-based UI that minimizes data-entry friction for field sales teams.
In its favor
Why people choose Mazrica Sales (formerly Senses)
The signal that keeps Mazrica Sales (formerly Senses) on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
AI-driven opportunity scoring and risk analysis using historical deal data to recommend next actions, sourced from G2 reviews and ITReview Leader awards across SFA and CRM categories.
Card-based deal pipeline UI with drag-and-drop stage transitions that reduces onboarding friction for sales reps unfamiliar with traditional CRM workflows.
OCR名片 (business card) scanning and AI-powered contact deduplication that accelerates initial CRM population from field encounters.
Native Japanese-language interface and local customer support cited in comparison reviews as a key differentiator for Japan-based SMBs evaluating SFA tools.
Pre-built Workato connector and iPaaS integration support that reduces friction for teams with existing Japanese cloud toolchains.
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.
Reasons to switch
Why people leave Mazrica Sales (formerly Senses)
The recurring reasons buyers give for replacing Mazrica Sales (formerly Senses). Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Mazrica Sales (formerly Senses) fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Mazrica Sales (formerly Senses) pricing overview
Pricing is per-user on the Starter tier (minimum 5 users) and published as flat monthly rates for Growth and Enterprise tiers. All plans require a minimum 1-year contract. No free trial or free tier is publicly available.
Starter
Tier 1 of 3
¥27,500/month (5 users minimum, ¥5,500/user/month)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Mazrica Sales (formerly Senses)'s schedule — see our quote-based pricing →
What gets migrated
Mazrica Sales (formerly Senses) object support
Object-by-object support for Mazrica Sales (formerly Senses) migrations. Per-pair details surface during scoping.
Contacts
Fully supportedContacts are the core CRM record in Mazrica Sales. The API exposes full CRUD operations plus bulk registration endpoints. We map contact fields 1:1 and preserve lifecycle stage assignments which drive automation workflows in the destination system.
Companies
Mapping requiredCompany records store enterprise-level data including financial info, press releases, and securities filings pulled from external sources. We handle field-level mapping as company names and identifiers vary significantly between Japanese business registries and international CRMs.
Opportunities
Fully supportedOpportunities (案件) use a card-based Kanban pipeline with drag-and-drop stage changes. We preserve stage names, amounts, expected close dates, and owner assignments. Custom pipeline stages require schema mapping at migration time.
Activities
Fully supportedActivities (行動) are time-stamped engagement records linked to Contacts and Opportunities. We preserve the full activity timeline including activity type, date, owner, and related notes. Bulk activity imports are supported via the ContactActions batch endpoint.
Lifecycle Stages
Mapping requiredLifecycle Stage is a configurable property on Contacts that drives automation triggers. The platform exposes a dedicated LifecycleStageSetting API endpoint. We map existing stage values and flag any records without a stage assignment, which can silently break inbound automation rules.
Custom Objects
Mapping requiredCustom Objects are user-defined data structures with their own schema definitions accessible via the CustomObjectSetting and CustomObjects API endpoints. Bulk read/write/delete operations are available. We read the live schema definition before migration and generate destination-side field mappings dynamically.
Users/Owners
Mapping requiredUser records carry roles and team assignments that gate permission sets in the platform. We map owner IDs to destination users and flag any orphaned ownership chains where the owning user does not exist in the target system.
Attachments
Not in this platformFile attachments associated with Contacts or Opportunities are not exposed via the documented v1 REST API. We do not migrate binary attachments through the API path and advise customers to export these manually via the web UI before migration cutoff.
Reports/Dashboards
Not in this platformSaved reports and dashboard configurations are not accessible via the public API. We do not migrate analytics artifacts; these must be rebuilt in the destination platform post-migration.
| Object | Support | Notes |
|---|---|---|
| Contacts | Fully supported | Contacts are the core CRM record in Mazrica Sales. The API exposes full CRUD operations plus bulk registration endpoints. We map contact fields 1:1 and preserve lifecycle stage assignments which drive automation workflows in the destination system. |
| Companies | Mapping required | Company records store enterprise-level data including financial info, press releases, and securities filings pulled from external sources. We handle field-level mapping as company names and identifiers vary significantly between Japanese business registries and international CRMs. |
| Opportunities | Fully supported | Opportunities (案件) use a card-based Kanban pipeline with drag-and-drop stage changes. We preserve stage names, amounts, expected close dates, and owner assignments. Custom pipeline stages require schema mapping at migration time. |
| Activities | Fully supported | Activities (行動) are time-stamped engagement records linked to Contacts and Opportunities. We preserve the full activity timeline including activity type, date, owner, and related notes. Bulk activity imports are supported via the ContactActions batch endpoint. |
| Lifecycle Stages | Mapping required | Lifecycle Stage is a configurable property on Contacts that drives automation triggers. The platform exposes a dedicated LifecycleStageSetting API endpoint. We map existing stage values and flag any records without a stage assignment, which can silently break inbound automation rules. |
| Custom Objects | Mapping required | Custom Objects are user-defined data structures with their own schema definitions accessible via the CustomObjectSetting and CustomObjects API endpoints. Bulk read/write/delete operations are available. We read the live schema definition before migration and generate destination-side field mappings dynamically. |
| Users/Owners | Mapping required | User records carry roles and team assignments that gate permission sets in the platform. We map owner IDs to destination users and flag any orphaned ownership chains where the owning user does not exist in the target system. |
| Attachments | Not in this platform | File attachments associated with Contacts or Opportunities are not exposed via the documented v1 REST API. We do not migrate binary attachments through the API path and advise customers to export these manually via the web UI before migration cutoff. |
| Reports/Dashboards | Not in this platform | Saved reports and dashboard configurations are not accessible via the public API. We do not migrate analytics artifacts; these must be rebuilt in the destination platform post-migration. |
Gotchas
What to watch for in Mazrica Sales (formerly Senses) migrations
Issues we've hit on past Mazrica Sales (formerly Senses) migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
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
| Severity | Issue |
|---|---|
| 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 |
Leaving Mazrica Sales (formerly Senses)?
Where Mazrica Sales (formerly Senses) customers move next
12 destinations Mazrica Sales (formerly Senses) can migrate to.
How a Mazrica Sales (formerly Senses) migration works
Four steps, Mazrica Sales (formerly Senses)-specific
Connect
Not publicly documented in current API reference into Mazrica Sales (formerly Senses). Scopes limited to read-only on the data we move.
Map
We translate Mazrica Sales (formerly Senses)-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Mazrica Sales (formerly Senses) quirks before production.
Migrate
Full migration with Mazrica Sales (formerly Senses) rate-limit handling. Rollback available throughout.
FAQ
Mazrica Sales (formerly Senses) migration FAQ
Answers to the questions buyers ask most during Mazrica Sales (formerly Senses) migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Mazrica Sales (formerly Senses) migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Mazrica Sales (formerly Senses).
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Mazrica Sales (formerly Senses) setup and destination — written quote back within a business day.