Migrate from Mazrica Sales (formerly Senses) to monday CRM

Mazrica Sales Contacts map directly to Monday.com CRM People. We preserve name, email, phone, company association, owner assignment, and lifecycle stage. The lifecycle stage value from Mazrica Sales migrates as a custom People column (text or tag) in Monday.com CRM so that reporting continuity holds after migration. We resolve the owner assignment by matching Mazrica Sales owner email against Monday.com team member email, flagging any unmapped owners in a reconciliation queue.

Mazrica Sales Company records map to Monday.com CRM Organizations. We preserve company name, domain, address fields, industry, financial data (where applicable), and the hierarchical parent-child structure. Organization is created before any People import so that the Organization lookup is satisfied at the moment of People insert. Multi-level hierarchies in Mazrica Sales (parent and child companies) map to Organization sub-groups in Monday.com CRM where the customer maintains the hierarchy post-migration.

Mazrica Sales Opportunities (案件) map to Monday.com CRM Deals as board items. We preserve stage name, deal amount, expected close date, owner, and any custom field values. Each Mazrica Sales pipeline becomes a separate Monday.com CRM board. Custom pipeline stages in Mazrica Sales map to Monday.com CRM column values in the Deal board. Stage probability percentages migrate as a numeric column in Monday.com CRM. The card-based Kanban drag-and-drop experience in Mazrica Sales maps directly to Monday.com's board column layout.

Mazrica Sales Activities — calls, emails, meetings, and tasks with timestamps, owners, and related notes — map to Monday.com CRM Updates on the related Deal or People item. We preserve activity type, date, owner, duration (for calls), and note content as an Update entry with a structured label (e.g., [Call], [Email], [Meeting]) so that the activity timeline is readable in Monday.com. High-volume activity migrations are chunked to respect API batch limits and preserve the chronological ordering of the timeline.

Mazrica Sales Lifecycle Stage is a configurable Contact property that drives automation triggers. We map existing stage values to a custom People column in Monday.com CRM (implemented as a tag or text column depending on the customer's preferred filtering method). The LifecycleStageSetting API endpoint exposes the stage matrix; we read it during scoping to confirm which stages are active and whether any gaps exist in the stage assignment.

Mazrica Sales Custom Objects are user-defined data structures with their own schema definitions accessible via the CustomObjectSetting and CustomObjects API endpoints. We map each Custom Object to a dedicated Monday.com CRM board with columns matching the source schema. Bulk read/write operations are available on the source; we chunk Custom Object payloads during export to respect API batch limits and preserve field-level custom properties. Lookup relationships between Custom Objects and standard objects (Contact, Opportunity) are resolved at migration time by matching the referenced record ID to the migrated destination ID.

Mazrica Sales User records carry roles and team assignments that gate permission sets. We map owner IDs to Monday.com CRM team members by email match. Any Mazrica Sales owner without a matching Monday.com user is held in a reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId references are required on most migrated records.

Binary file attachments associated with Contacts, Companies, or Opportunities are not exposed via the documented Mazrica Sales v1 REST API. We do not migrate attachments through the API path. We advise customers to export attachments separately through the Mazrica Sales UI or direct database export and re-upload them manually in Monday.com CRM post-migration. The lack of attachment access is a documented API limitation on the Senses-era endpoint.