Migrate from Mazrica Sales (formerly Senses) to Salesforce Sales Cloud

Mazrica Contacts with lifecycle stage values indicating unqualified prospects (lead, marketing qualified) map to Salesforce Lead. Contacts with sales-qualified or customer lifecycle stages map to Salesforce Contact attached to an Account. We compute the split using Mazrica's lifecycle_stage property against the customer's stage matrix and preserve the original Mazrica lifecycle stage in a custom field original_lifecycle_stage__c on both Lead and Contact for audit. Any Contact lacking a lifecycle stage value goes to a reconciliation queue because it would silently exclude from automated workflows in both platforms.

Mazrica Company records map to Salesforce Account. The company name becomes the Account Name; the domain field maps to Website. Company hierarchy (parent-subsidiary relationships) maps to Salesforce Account Hierarchy if configured, or to a custom parent-account lookup field. External company data (financial info, press releases) sourced from third-party integrations in Mazrica does not transfer via API and is flagged for manual re-enrichment in Salesforce via Data.com, Dun & Bradstreet, or a similar enrichment tool.

Mazrica Opportunities map directly to Salesforce Opportunity. The card-based pipeline stage name maps to Salesforce StageName by explicit value translation (we generate the mapping table during scoping). The amount, expected close date, owner, and probability percentage migrate directly. Custom pipeline stages defined by the customer in Mazrica require pre-configuration of Salesforce stage values and Record Types before migration so that stage probabilities are preserved correctly.

Mazrica's card-based Kanban pipeline (with custom stage names and card colors) translates to Salesforce StageName values within a Sales Process. Each Mazrica pipeline becomes a Salesforce Record Type with its own Sales Process that whitelists only the relevant stage values. Stage probability percentages migrate from Mazrica to Salesforce StageProbability, rounded to the nearest integer allowed by Salesforce.

Mazrica Activity records (calls, meetings, tasks, notes) map to Salesforce Task and Event objects. Call engagements map to Task with TaskSubtype=Call; meeting engagements map to Event with StartDateTime and EndDateTime preserved; task-type activities map to Task. The WhoId on Salesforce Task points to the migrated Contact or Lead; the WhatId points to the related Opportunity or Account. Activity timestamps are preserved as ActivityDate to maintain the timeline order that sales reps rely on.

Mazrica Custom Objects (defined via CustomObjectSetting and CustomObjects API endpoints) map to Salesforce custom objects of matching API name with __c suffix. We pre-create the destination schema including all custom fields, field types, and lookup relationships in a Salesforce Sandbox before migration begins. Custom object records with lookup dependencies on Accounts, Contacts, or Opportunities require those parent records to exist first, so we import parent objects before custom object records.

Mazrica User records (with roles and team assignments) map to Salesforce User by email address match. Owner IDs on Mazrica Contact, Company, and Opportunity records are resolved against the Salesforce User table at migration time. Any Mazrica Owner without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Salesforce Users cannot own records; the customer decides whether to provision inactive Users for historical ownership or reassign to active Users.

Mazrica's configurable lifecycle stage values (exposed via LifecycleStageSetting API) map to Salesforce Lead Status values for Leads and to a custom picklist field on Contact. We build the translation table during scoping and deploy it as part of the Salesforce schema configuration. Stage values without a Salesforce equivalent are flagged and added as new Lead Status values before migration.

Mazrica's AI-generated risk scores and order forecasts are computed at migration time and stored as record properties rather than as independent data objects. We extract the most recent risk score, confidence level, and next-action recommendation and store them as custom fields on the Salesforce Opportunity (e.g., mazrica_risk_score__c, mazrica_ai_confidence__c). Ongoing AI scoring after cutover requires Salesforce Einstein Opportunity Scoring or a third-party Revenue Intelligence app to be configured separately.

Binary file attachments associated with Mazrica Contacts, Companies, or Opportunities are not accessible via the documented v1 REST API. We do not migrate attachments through the API path. We document the count and location of attachments per record during scoping so the customer's admin can export them manually via Mazrica's UI and upload them to Salesforce as ContentDocument records post-migration.

Saved reports and dashboard configurations are not accessible via the Mazrica public API. We do not migrate analytics artifacts. We deliver a written inventory of every Mazrica report and dashboard with its name, filter criteria, and output columns, which the customer's admin uses to rebuild equivalent Salesforce Reports and Lightning Dashboards post-migration.

Mazrica tags applied to Contacts, Companies, or Opportunities as label properties map to Salesforce multi-select picklist fields. We extract all distinct tag values during scoping and configure the picklist options in Salesforce before migration. Tags used for segmentation also map to Salesforce Topics with TopicAssignment records if the customer requests topic-based organization.