Migrate from Mazrica Sales (formerly Senses) to Pipedrive

Mazrica Contact records map to Pipedrive Person. The contact's email becomes the Person's primary email field and serves as the deduplication key during import. We preserve Mazrica lifecycle stage values in a custom text field (mazrica_lifecycle_stage__c) on Person since Pipedrive has no native lifecycle stage object. Owner assignments map by email match against Pipedrive User records in the destination org.

Mazrica Company records map to Pipedrive Organization. The company name becomes the Organization name; financial data and securities filings pulled from external sources in Mazrica (a Mazrica Enterprise feature) map to custom fields on Organization. Organization is created before Person import so the Person.organization_id relationship is satisfied at insert time.

Mazrica Opportunity (案件) records map to Pipedrive Deal. Stage name, deal amount, expected close date, and owner assignment migrate directly. Mazrica custom pipeline stages require pre-configuration in Pipedrive before migration because Pipedrive's pipeline stages must exist in the destination before a Deal can be assigned to them. We flag any Mazrica stage that has no Pipedrive equivalent and create it during the schema preparation phase.

Mazrica Activities (行動) are time-stamped engagement records that map to Pipedrive Activity records of the corresponding type (call, meeting, task, email). We map activity type, date, owner, and related notes. Bulk activity payloads are chunked to respect Pipedrive's API rate limits. The activity timeline ordering is preserved by setting the Pipedrive Activity's done_date to the original Mazrica timestamp. Parent record resolution (linking activities to Person and Deal) is done via email lookup for Person and deal_id lookup for Deal.

Mazrica Lifecycle Stage is a configurable Contact property exposed via the LifecycleStageSetting API endpoint. Pipedrive has no native equivalent. We create a custom field mazrica_lifecycle_stage__c on the Person object, preserve the original stage label as a string value, and document the stage mapping for the customer's admin to use in Pipedrive Filters or Automations if needed. No automation rebuild is included in migration scope.

Mazrica Custom Objects have independent schema definitions and bulk API endpoints. Pipedrive does not support independent custom object entities; custom properties are stored as custom fields on standard objects (Person, Organization, Deal). We pre-create the equivalent Pipedrive custom fields during schema preparation, matching field types (text, number, date, dropdown) to Pipedrive's supported field types. Any Mazrica Custom Object with relationships to standard objects maps those relationships to Pipedrive's linked_organization_value or linked_person_value fields.

Mazrica User records carry roles and team assignments that gate permission sets. We map owner IDs to Pipedrive User records by email match. Any Mazrica Owner without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes. The Pipedrive User must be active and have the appropriate permission set before owner assignments can be written.

Mazrica tag values on Contacts, Companies, and Opportunities map to Pipedrive Labels on Person, Organization, and Deal respectively. Pipedrive Labels are a flat tagging system without hierarchy. Multi-value tags on a single Mazrica record become multiple Pipedrive Labels on the equivalent record. We migrate all tag associations at the record level.

File attachments associated with Mazrica Contacts, Companies, or Opportunities are not exposed via the documented v1 REST API. We do not migrate binary attachments through the API path. We advise customers to export attachments from Mazrica manually before migration cutover and re-upload to Pipedrive's Files feature post-migration. This step is documented in the pre-migration checklist delivered during scoping.

Saved reports and dashboard configurations are not accessible via Mazrica's public API. We do not migrate analytics artifacts. We deliver a written inventory of every named Mazrica report with its filters, date ranges, and visualizations so the customer's Pipedrive admin can rebuild equivalent Insights reports in Pipedrive. Report rebuild is outside migration scope.