Migrate from Mazrica Sales (formerly Senses) to Freshsales

Mazrica Sales Contacts map to Freshsales Contacts 1:1. We preserve the lifecycle_stage property as a custom field on the Freshsales Contact (e.g., lifecycle_stage__c) because Freshsales does not have a native lifecycle stage property equivalent. Contact ownership resolves by email match to Freshsales User. Records missing an email address receive a placeholder owner pending admin resolution.

Mazrica Sales Companies map to Freshsales Accounts. The company name becomes the Account Name; website domain maps to the Account Website field. We use company name as the dedupe key during import to prevent duplicate Account creation. Financial info, press releases, and securities data from Mazrica Sales Company records map to custom Account fields if defined.

Mazrica Sales Opportunities map to Freshsales Deals. The card-based stage name (e.g., リード, 提案, 交渉, 受注) maps to Freshsales Deal Stage within the target pipeline. Deal amount, expected close date (expected_close_date), and owner assignment migrate directly. Custom pipeline stages require Freshsales pipeline pre-configuration before migration.

Mazrica Sales Activities (call, email, meeting, task, note) map to Freshsales Task or Event records. Activity type, date, owner, and related notes transfer directly. Activity timestamp ordering preserves via ActivityDate on Task or Start Time on Event. Bulk Activity payloads are chunked to respect API batch limits and maintain timeline integrity.

Mazrica Sales LifecycleStageSetting values migrate as a custom text or picklist field on Freshsales Contact. We pre-create the custom field during schema setup and populate it from the lifecycle_stage property on each Mazrica Sales Contact. Automation triggers relying on lifecycle stage in Mazrica Sales require rebuilding in Freshsales using Workflows post-migration.

Mazrica Sales CustomObjectSetting and CustomObjects migrate to Freshsales Custom Objects (Pro tier and above required). We pre-create the destination schema including all custom fields, lookup relationships, and validation rules before data import. Starter tier on Freshsales does not support Custom Objects; if the customer is on Starter, we recommend upgrading to Pro or migrating without custom objects and rebuilding as standard objects.

Mazrica Sales Users map to Freshsales Users by email match. Roles and team assignments from Mazrica Sales map to Freshsales Roles and Teams where possible, though permission models differ. Any Mazrica Sales Owner without a matching Freshsales User enters a reconciliation queue for admin provisioning before record import resumes.

Binary file attachments on Mazrica Sales Contacts or Opportunities are not accessible via the public API. We do not migrate attachments through the API path. We provide a structured export of attachment metadata (filename, record association, size) and a written guide for manual download and re-upload to Freshsales. This step requires the customer to perform the actual file transfer with our metadata map as the guide.