Migrate from Mazrica Sales (formerly Senses) to HubSpot

Mazrica contacts migrate directly to HubSpot contacts. The Mazrica contact record carries name, email, phone, job title, company link, lifecycle stage, and AI-prediction scores. All standard properties map to HubSpot's built-in contact properties. Custom properties are created as HubSpot custom properties before migration. Mazrica contact IDs are stored as Source_System_ID__c for traceability.

Mazrica companies map to HubSpot companies. Company name, domain/website, industry, employee count, annual revenue, and address fields map to HubSpot's corresponding company properties. Parent-company hierarchies in Mazrica map to HubSpot's parent-company association field. Multi-contact companies are handled by linking all contacts to the migrated company record.

Mazrica cases are the core sales-record object, containing deal name, amount, stage, close date, owner, and activity history. Cases map to HubSpot deals with pipeline-stage mapping: each Mazrica stage becomes a HubSpot deal stage within a designated pipeline. Case-card metadata (risk level, AI prediction scores, next action) is preserved as custom properties on the deal. Case-to-contact association migrates as the deal's primary contact association.

Mazrica records activities as Contact Action objects with type, timestamp, owner, and linked contact/case IDs. Types map to HubSpot engagement types: call → HubSpot call, email → HubSpot email, meeting → HubSpot meeting. Each engagement is written to the contact's timeline in HubSpot. Original timestamps and owner IDs are preserved. Case-linked activities attach to the migrated deal via association.

Mazrica notes map to HubSpot notes. Rich-text formatting is preserved. Notes are associated to the migrated contact or deal record by ID lookup. If the note references a Mazrica case ID, the association redirects to the corresponding HubSpot deal after migration.

Mazrica custom objects migrate 1:1 to HubSpot custom objects (available on HubSpot Enterprise tiers). The custom object schema — field names, types, and labels — is read from Mazrica's custom_object_definition API endpoint and recreated in HubSpot using HubSpot's custom object API. All data rows transfer with original IDs preserved as a source reference field.

HubSpot does not have a native lifecycle_stage equivalent on the Mazrica side. We create a custom pick-list property in HubSpot (Lifecycle_Stage__c or matching the exact label used in Mazrica) and populate it from Mazrica's contact-level lifecycle data. Standard HubSpot lifecycle values are used when they match; custom stage names are preserved as-is in the pick-list.

Mazrica owner IDs resolve by email match against HubSpot users. If a Mazrica owner email matches an existing HubSpot user, records are assigned to that user. Unmatched owners are flagged before migration for your team to either invite the user to HubSpot or assign records to a fallback owner. No record lands without a valid HubSpot owner.

Files attached to Mazrica contacts, companies, or cases are downloaded from Mazrica's file storage and re-uploaded to HubSpot's file management. Files are associated to the corresponding migrated record. HubSpot's 25MB per-file limit is enforced; files exceeding this are flagged for manual review. Japanese file names are preserved with UTF-8 encoding throughout.

Mazrica's AI predicts deal probability, estimated contract date, and estimated contract amount per case. These are not standard CRM fields in HubSpot. We create custom number and date properties on the HubSpot deal object (AI_Probability__c, AI_Predicted_Close__c, AI_Predicted_Amount__c) and populate them from Mazrica's case data. This preserves historical AI intelligence even though HubSpot's native AI tools will recalculate scores going forward.