Migrate from Mazrica Sales (formerly Senses) to Microsoft Dynamics 365 Sales

Mazrica Sales Contacts with a Lifecycle Stage value of 導入検討 or 訪問提案 map to Dynamics 365 Lead. Contacts with Lifecycle Stage of 商談中, 契約済, or 取引再開 map to Dynamics 365 Contact attached to an Account. We preserve the original Mazrica Sales lifecycle stage in a custom field mz_original_lifecycle__c on both Lead and Contact for audit trail and reporting continuity. The split rule is defined during scoping against the customer's actual stage matrix and validated in the sandbox phase before production migration.

Mazrica Sales Company records map directly to Dynamics 365 Account. The Mazrica company_name becomes Account Name, and the registered_address fields map to Address composite fields. We use company_id from Mazrica Sales as the dedupe key during import to prevent duplicate Account creation. Account is created before Contact import so that the primarycontactid lookup and parentaccountid relationship are satisfied at the moment of Contact insert.

Mazrica Sales Opportunities (案件) map to Dynamics 365 Opportunity. The Mazrica Sales pipeline stage (pipeline_name and stage_name) maps to a Microsoft Dynamics 365 Sales Process and stage value that we configure before migration. Amount, estimated_close_date, and owner_id migrate directly. Custom pipeline stage names from Mazrica Sales become custom stage values in Dynamics 365 that we add to the relevant Sales Process via the customizations API.

Each Mazrica Sales deal pipeline becomes a Dynamics 365 Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values. If the customer has multiple pipelines in Mazrica Sales representing different business lines, each maps to its own Record Type so that stage values remain scoped per line of business and Page Layouts render the correct fields per pipeline.

Mazrica Sales Activities (行動) with activity_type of 電話, 訪問, メール, or 備考 map to Dynamics 365 PhoneCall, Appointment, Email, and Task respectively. We preserve the activity date, owner, related_contact_id, and related_opportunity_id as WhatId and regarding_objectid references in Dataverse. Bulk activity payloads are chunked to respect the Dataverse batch request limits and loaded via the web API with rate-limit backoff.

Mazrica Sales LifecycleStageSetting values migrate as a custom text or picklist field mz_lifecycle_stage__c on both Lead and Contact. If the customer uses the Dynamics 365 Field Service or Sales_insights add-on that supports state modeling, we map lifecycle stage transitions to state transitions for automated state-based flows. The original Mazrica stage values are never discarded because they serve as the audit reference for historical pipeline reporting.

Mazrica Sales Custom Objects with user-defined schema (accessed via CustomObjectSetting and CustomObjects API endpoints) map to Dataverse custom tables created via Power Apps or the customizations XML. We pre-create the destination schema in a sandbox environment including all custom columns, lookup relationships to standard entities (Account, Contact, Opportunity), and any validation rules before data import. Custom object naming follows the Dataverse table name convention and inherits the publisher prefix from the target solution.

Mazrica Sales Users with owner_id references on Contact, Company, Opportunity, and Activity records map to Dynamics 365 User records. We resolve by matching the Mazrica Sales user email against the Azure Active Directory-backed User table in the destination Dynamics 365 org. Owners without a matching User go to a reconciliation queue for the customer's admin to provision before record import resumes. Orphaned ownership chains are flagged in the scoping report.

Mazrica Sales Product records (if present) map to Dynamics 365 Product. Product name, product code (hs_sku equivalent), and unit map directly. We create the corresponding Price List and Price List Item entries in Dynamics 365 before Opportunity import so that opportunity_product associations resolve correctly during migration.

Binary file attachments associated with Mazrica Sales Contacts, Companies, or Opportunities are not exposed via the senses-open-api v1 REST endpoint. We do not migrate attachments through the API. We advise customers to export attachments via Mazrica Sales bulk export (if available manually) and upload to a SharePoint Document Library that we then connect to Dynamics 365 via the native SharePoint integration. The resulting SharePoint URL is stored in a custom field on the relevant record for reference.