Migrate from Prospects CRM to Salesforce Sales Cloud

Prospects CRM stores all people as Contact records with a status property (e.g., New, Contacted, Customer). Salesforce splits these into Lead (unqualified) and Contact (qualified) objects. We route records by Prospects status: 'Customer' and 'Won Deal' land as Salesforce Contacts; everything else routes to Salesforce Leads. Status value preserved as a custom field on both objects for reporting continuity.

Direct map. Prospects company records map to Salesforce Accounts. Parent-child company hierarchies (sub-company links) map to Salesforce ParentId. Multi-company associations on a single Prospects contact collapse to one primary AccountId plus Account Contact Relations in Salesforce for any secondary companies.

Direct map. Prospects deals map to Salesforce Opportunities. Pipeline stages map to Opportunity StageName values. Pipeline name maps to Salesforce RecordTypeId so each Prospects pipeline gets its own record type with page-layout-scoped stage values. Deal owner resolved by email match to Salesforce users before migration.

Prospects pipeline maps to a Salesforce Sales Process keyed by Record Type. Each pipeline requires its own record type in Salesforce so stage pick-list values are scoped correctly per business unit. We deliver a record-type-and-page-layout setup plan as part of the migration package so Salesforce admins can pre-create the schema before data lands.

Stage names mapped value-by-value per Record Type. Stage probability and forecast category re-applied based on Salesforce's stage-history model. Stage-entered timestamps preserved as custom datetime fields (Stage_Entered__c) for reporting continuity across the migration boundary. We also retain any custom stage ordering or naming conventions from Prospects CRM as a lookup table to ensure consistency in reporting and dashboard filters after cutover.

Magic Matrix RFM segment scores and classifications have no native Salesforce equivalent. We migrate these as custom pick-list or text fields (RFM_Segment__c, Magic_Matrix_Score__c) on both Lead and Contact. The underlying order-frequency and revenue data that feeds Magic Matrix also migrates as custom numeric fields so you can rebuild the segmentation logic in Salesforce Reports.

Prospects calls and emails map to Salesforce Tasks with Type='Call' or Type='Email'. Meetings map to Events with original start and end times preserved. Notes map to Salesforce Notes (not legacy Note object). Original timestamps, owners, and parent-record links preserved. Task WhoId links to the correct Lead or Contact based on the split routing from the contact mapping step.

Prospects custom objects (Enterprise tier) map 1:1 to Salesforce custom objects. Custom object associations that use Prospects N:N model need Salesforce junction objects — we surface these in the migration plan and create the junction schema before loading data. Custom object __c naming conventions applied per Salesforce metadata rules.

Prospects file attachments on records re-upload to Salesforce Files (ContentDocument / ContentVersion model). File size limits apply: Salesforce default 25MB per file. Inline images in notes are downloaded and re-hosted as Salesforce Files. File original author and create date preserved in ContentVersion metadata.

Prospects CRM's native integrations with Unleashed, Katana, Cin7, Xero, and QuickBooks are configuration-layer connections with no data record to migrate. We export the integration configuration (API endpoints, field mappings, sync rules) as a reference JSON document so your Salesforce admin or integration partner can rebuild the connection using AppExchange apps or MuleSoft.

Prospects owner records resolved by email match against Salesforce Users. Unmatched owners are flagged before migration — your team either provisions them in Salesforce first or assigns their records to a fallback owner. No record lands without a Salesforce OwnerId. Active/inactive status in Prospects maps to Salesforce User.IsActive for accurate license planning.

Prospects CRM workflow rules (task triggers, email-on-stage-change, owner assignment rules) are automation-layer configurations with no data migration path to Salesforce Flow. We export workflow definitions in a structured JSON reference so your Salesforce admin can rebuild each rule as a Screen Flow or Autolaunched Flow. The rebuild effort is bounded and documented per rule.