Migrate from matrix to Salesforce Sales Cloud

Matrix contacts without a converted status field route to Salesforce Lead; contacts marked as customers or with deal associations route to Salesforce Contact. The split logic applies at migration time based on Matrix contact properties. Unconverted contacts land as Salesforce Leads; converted or deal-associated contacts become Salesforce Contacts.

Matrix companies map directly to Salesforce Accounts. Parent-child company hierarchies in Matrix use the Parent_Company_ID field and translate to Salesforce's ParentId lookup. Contacts without a primary company association receive a default Account or are flagged for manual assignment. We also map industry and website fields, and apply duplicate detection rules to prevent overlapping Accounts based on name and domain.

Matrix deals become Salesforce Opportunities. The deal name maps to Opportunity.Name, amount maps to Amount, close date maps to CloseDate, and owner resolves via email match to Salesforce users. Pipeline and stage information requires additional mapping to Salesforce Sales Processes and Record Types.

Matrix pipelines do not have a direct Salesforce equivalent. Each Matrix pipeline translates to a Salesforce Sales Process associated with a Record Type. This requires pre-creating the Record Type in Salesforce before the migration run so Opportunity.StageName values can be scoped correctly.

Stage names require value-by-value mapping between Matrix stage values and Salesforce Opportunity Stage values per Record Type. Probability percentages and forecast category assignments are re-applied from Salesforce's stage configuration. Stage transition timestamps are preserved as custom datetime fields. We also ensure that stage order reflects the intended sales process sequence, and configure stage-dependent picklist dependencies for product lines if needed.

Matrix activity logs split into Salesforce objects by type: calls and emails become Tasks with Type set appropriately, meetings become Events with start and end times, and text notes become Salesforce Notes (modern object). Original timestamps, owners, and parent-record links are preserved through WhoId and WhatId lookups.

Matrix custom fields on any object become Salesforce custom fields with the __c suffix. Text, number, date, and pick-list types map to their Salesforce equivalents. Multi-select pick-lists in Matrix require a custom field with the MultiSelectPicklist type. Field-level security settings are applied per Salesforce profile post-migration.

Matrix file attachments on records re-upload to Salesforce Files linked via ContentDocumentLink. File size limits apply (Salesforce default 25MB per file). Inline images in notes are downloaded, rehosted in Salesforce, and replaced with file references. Large files may require Salesforce CRM Content or Files sync configuration.

Matrix owner records resolve to Salesforce Users by email address match. Unmatched owners are flagged before migration — the team either creates Salesforce users first or assigns records to a fallback owner. System admin records without email are mapped to a designated Salesforce admin user.

Matrix integrations with third-party tools do not migrate. Each connected app must be reconfigured in Salesforce: OAuth connections, API keys, webhook endpoints, and embedded browser integrations are destination-side configurations. FlitStack provides a connection inventory list as part of the migration audit.

Matrix reports and dashboards are not migrated. The underlying data (opportunities, contacts, activities) transfers, but report definitions must be rebuilt in Salesforce Reports and Salesforce Dashboards. FlitStack delivers a report mapping guide listing each source report and its recommended Salesforce equivalent.

Matrix workflows, automation rules, and sequence logic do not migrate to Salesforce. These must be rebuilt using Salesforce Flow or Process Builder. We export Matrix workflow definitions as a structured JSON reference document that your Salesforce admin can use to recreate automation logic in Flow.