Migrate from Mazrica Sales (formerly Senses) to HighLevel

Mazrica Sales Contacts map directly to GoHighLevel Contacts. First name, last name, email, phone, and address fields migrate 1:1. We preserve the lifecycle stage value (from LifecycleStageSetting API) in a GoHighLevel contact custom field named lifecycle_stage__c so that automation triggers in GoHighLevel can reference it after migration. Any contact missing a lifecycle stage value is flagged in the reconciliation report with a warning that automation rules depending on that field may not fire.

Mazrica Sales Company records have no native GoHighLevel equivalent because GoHighLevel does not have a separate Companies or Accounts object. Company-level data (industry, employee count, annual revenue, external enrichment data, press releases) migrates as contact custom fields on the primary Contact record. If multiple Mazrica Sales Contacts are linked to the same Company, we write the company data to the first-linked Contact and flag duplicates for manual consolidation in GoHighLevel.

Mazrica Sales Opportunities (案件) map to GoHighLevel Opportunities. Deal amount, expected close date, stage name, owner assignment, and related contact all migrate 1:1. Custom pipeline stages in Mazrica Sales must be pre-created as GoHighLevel Opportunity custom fields or status values before migration so that stage names are preserved without defaulting to GoHighLevel stage placeholders.

Mazrica Sales Activities (行動) map to GoHighLevel Tasks. Activity type (call, email, meeting, note, custom) migrates as a GoHighLevel task custom field or tag. The original timestamp, owner, and related contact link all preserve. We chunk bulk activity imports to respect GoHighLevel API rate limits and set task status based on activity completion in Mazrica Sales.

Mazrica Sales Custom Objects (user-defined schemas via CustomObjectSetting and CustomObjects API) require schema pre-creation in GoHighLevel before any data moves. GoHighLevel's Custom Values are key-value pairs attached to contacts or opportunities, not standalone objects, so complex Mazrica Custom Object relationships with multiple fields and lookup dependencies flatten to multiple custom fields on the related standard object. We document the full original schema and the flattening strategy in the scoping report.

Mazrica Sales Lifecycle Stages are a configurable property exposed via the LifecycleStageSetting API. We query the active stage values from Mazrica Sales, create a matching picklist field in GoHighLevel Contacts, and populate it for every migrated contact. If the customer uses lifecycle-stage-triggered workflows in Mazrica Sales, we document the trigger conditions as part of the automation inventory for the admin to rebuild in GoHighLevel's workflow builder.

Mazrica Sales Users and Owner assignments on Contacts, Companies, Opportunities, and Activities resolve by email match against GoHighLevel Users. Any Owner without a matching GoHighLevel User enters a reconciliation queue for the admin to provision before record import resumes. Owner reassignment after migration is outside scope; we preserve the original owner reference so the admin can remap post-import if needed.

File attachments associated with Mazrica Sales Contacts, Companies, or Opportunities are not accessible via the documented v1 REST API. We do not migrate binary attachments and flag them in the scoping report so the customer can export them manually from the Mazrica Sales web interface and re-upload to GoHighLevel after migration. Links to external file storage are preserved as URL custom fields where present.