Migrate from matrix to Freshsales

Matrix leads map directly to Freshsales leads. Freshsales leads have their own field schema separate from contacts — any Matrix lead custom properties that have no Freshsales native equivalent are created as custom fields on the Lead module before migration runs.

Matrix contacts map to Freshsales contacts with a direct field-to-field correspondence. The mapping preserves the contact's email address and display name, which serve as the primary deduplication key within Freshsales. Contacts without a primary company association land in Freshsales with a null account_id, and these records are flagged in the reconciliation report for manual association after migration.

Matrix companies map to Freshsales accounts. Company domain, industry, employee count, and annual revenue are preserved. Parent-company relationships in Matrix map to Freshsales Parent Account lookups — the parent account must be migrated first to avoid circular-reference errors when the child account loads.

Matrix deals map to Freshsales deals. The deal's name, amount, close date, and stage are preserved. Pipeline-to-deal_pipeline assignment is resolved during the migration run so each deal lands in the correct Freshsales pipeline with the appropriate stage value from the source system.

Matrix pipeline metadata including name, associated stages, and stage probabilities are decomposed into their component parts and loaded into Freshsales deal_pipelines. Each Freshsales pipeline gets its stages configured with the correct probability values and status flags matching the source configuration.

Matrix activity records are mapped to Freshsales Sales Activities for calls and emails or to Tasks for standalone tasks. The original timestamp, duration, owner, and parent entity reference are preserved on the Freshsales record to maintain the full activity audit trail.

Matrix notes map to Freshsales notes, preserving the note body text and creation timestamp. Notes are linked to their parent record via Freshsales's entity-type and entity-id association model, allowing notes to be displayed in the context of the Contact, Account, or Deal they reference.

Matrix product records including name, SKU, unit price, and currency map to Freshsales Product Catalog entries. Products are migrated before deal line items so Freshsales can resolve product_id lookups on deals at import time and correctly associate line items with their source products.

Any Matrix contact custom field with no Freshsales native equivalent (for example, a text field tracking referral source) is pre-created on the Freshsales Contacts module using the API before record migration. The field name in Freshsales uses snake_case matching the source field label for consistency.

Matrix deal custom fields are pre-created on the Freshsales Deals module. Pipeline-specific deal properties that have no Freshsales equivalent are stored as custom fields on the deal record. The Freshsales API returns the new field IDs for mapping during the migration run.

Matrix custom objects are mapped to Freshsales custom objects. Freshsales requires custom object definitions to be created before records are loaded. N:N relationships from Matrix custom objects are represented in Freshsales via junction objects, which are included in the migration plan.

Matrix owner IDs are resolved by matching the owner's email address against Freshsales user accounts. Users with no match in Freshsales are flagged before migration — your team assigns a fallback owner or creates the user account before the migration run commits.

Matrix file attachments are downloaded from the source system and re-uploaded to Freshsales Files, linked to the parent record via entity-type and entity-id associations. Freshsales file size limits per plan apply (default 25MB per file). Inline images embedded in notes are extracted, re-hosted as Freshsales file attachments, and the note reference is updated accordingly.

Matrix tags are preserved as Freshsales tags on the corresponding record, maintaining tag names verbatim across systems. Tags associated with multiple record types (contact, account, deal) migrate independently under the same tag namespace, ensuring consistent taxonomy in Freshsales.