Migrate from Mazrica Sales (formerly Senses) to Twenty CRM

Mazrica Sales Contacts map to Twenty CRM Person records. We map standard fields (name, email, phone, address) and preserve the lifecycle stage value from Mazrica Sales as a custom field (original_lifecycle_stage__c) on the Person record for audit and reporting. Japanese-language name fields (姓, 名) map to givenName and familyName in Twenty's schema. Owner assignment from Mazrica Sales resolves to a Twenty User record by email match.

Mazrica Sales Company records map to Twenty CRM Company records. The company domain becomes the Website field. Financial info and external data sources from Mazrica Sales do not have direct Twenty equivalents; we map name, website, industry, and address fields. Any enrichment data (press releases, securities filings) that exists as structured fields in Mazrica maps to custom fields in Twenty that must be created during schema setup.

Mazrica Sales Opportunities map to Twenty CRM Opportunity records. We preserve deal amount, expected close date, and stage name. Custom pipeline stage names in Mazrica become Opportunity stage values in Twenty; these require manual configuration in Twenty's settings before migration. Owner assignments migrate by email-to-User resolution.

Each custom pipeline stage defined in Mazrica Sales becomes a named Stage value in Twenty's Opportunity settings. We extract the stage name and probability percentage (if set) from the Mazrica pipeline configuration during scoping and create a written stage mapping document. The customer configures the stages in Twenty before the Opportunity import phase runs.

Mazrica Sales Activities (calls, emails, meetings, tasks, notes) map to Twenty CRM Activity records. We preserve the activity type, date, owner, and related note content. The parent record reference (Contact or Opportunity) resolves to the corresponding Person or Opportunity in Twenty using the ID mapping table built during the Contact and Opportunity import phases.

Lifecycle Stage is a configurable property in Mazrica Sales exposed via the LifecycleStageSetting API. We map existing stage values to a custom field on Twenty Person records (lifecycle_stage__c). The stage values are preserved as-is; Twenty does not have a native lifecycle stage model, so the customer decides whether to use the original values as-is or remap them to a simplified set during the migration scoping phase.

Mazrica Sales custom objects with user-defined schemas map to Twenty CRM custom objects. We extract the schema definition (field names, types, lookup relationships) from the CustomObjectSetting API during scoping. The customer creates the equivalent custom object schema in Twenty's settings before migration; we do not auto-provision custom objects in Twenty because its custom object model requires manual definition in the UI or via configuration file.

Mazrica Sales Users with roles and team assignments map to Twenty CRM User records. We resolve owners by email match. Any Mazrica Sales User without a matching Twenty User goes to a reconciliation queue for the customer to provision before record import resumes. Inactive users in Mazrica Sales are flagged separately for decision on whether to provision as inactive users in Twenty.

If Mazrica Sales has product records (SKU, name, price), they map to Twenty CRM Product records. We extract product name, code, and standard price during the scoping phase and create a product mapping table. Products are imported before any Opportunity records that reference them to satisfy the lookup dependency.

Binary file attachments associated with Contacts or Opportunities in Mazrica Sales are not accessible via the documented v1 REST API. We do not migrate attachments through the API path. We advise customers to export attachments via Mazrica Sales's native export feature before migration and re-upload them manually in Twenty or via the Twenty API post-migration.