Migrate from Prospect CRM to Salesforce Sales Cloud

Prospect CRM Contact records map directly to Salesforce Contact. Standard fields (FirstName, LastName, Email, Phone, MailingAddress) migrate cleanly to Contact fields of equivalent type. We preserve any custom Contact properties as typed Salesforce custom fields (Text, Number, Date, or Picklist) using the __c suffix per Salesforce convention. RFM segmentation values (Recency, Frequency, Monetary tiers) migrate as a multi-select picklist custom field rfm_segment__c to maintain the customer classification without a custom object.

Prospect CRM Company records map to Salesforce Account. The company name becomes Account Name, billing and shipping addresses map to the corresponding Account address fields, and any custom Company properties migrate as custom fields on Account. Account is created before Contact import so that the AccountId lookup on Contact is satisfied at insert time, maintaining the parent-child relationship.

Prospect CRM Deals map to Salesforce Opportunity. Deal name becomes Opportunity Name, Deal value maps to Amount, and the pipeline stage assignment maps to StageName using an explicit stage mapping table we capture during scoping. OwnerId resolves via email match against the destination Salesforce User table. Closed-Lost and Closed-Won outcomes from Prospect CRM map to Salesforce Opportunity Stage values.

Prospect CRM pipeline stages (e.g., 'Quoted', 'Awaiting Stock', 'Negotiation') require explicit mapping to Salesforce Stage values. We capture stage name, stage order, and probability percentage during discovery and configure the Salesforce Sales Process to whitelist only the relevant stages for the migrated pipeline. Stage probabilities round to the nearest Salesforce-allowed integer.

Product catalog data including SKU, product name, description, and list price migrates from Prospect CRM to Salesforce Product2 records. Standard Pricebook entries are created during import. The stock-aware flag and live inventory linkage from Prospect CRM do not have a direct Salesforce equivalent; we map these to custom Boolean and text fields on Product2 and document the back-office reconnection requirement.

Prospect CRM's stock-aware quoting feature pulls live inventory from back-office systems into the quote view. This is a connection-level integration, not a data field, and cannot be migrated as data. We export the last-known stock status, available quantity, and stock flag values as custom Opportunity fields (pcs_stock_available__c, pcs_last_stock_check__c) and deliver a reconnection checklist for Unleashed, DEAR, or TradeGecko with required credentials and webhook URLs.

Prospect CRM activity history (calls, emails, meetings, tasks, notes) migrates as Salesforce Task and Event records. Call engagements map to Task with TaskSubtype = Call; meeting engagements map to Event with StartDateTime and EndDateTime preserved; emails map to Task with body content in Description; task engagements map to Task with Status and Priority preserved. ActivityDate timestamps are preserved to maintain the chronological timeline. We use the Salesforce Bulk API 2.0 for large activity volumes (100,000+ records) with parent-record lookup resolution on WhoId and WhatId.

Prospect CRM's Problem Pipelines object (used for tracking delivery issues, returns, and complaints) does not map to a standard Salesforce object by default. We migrate Problem records as Salesforce Cases with the original Status, Outcome, and linked Customer fields preserved. Problem type (delivery, return, complaint) maps to a custom Case Type picklist. If the destination org does not include Service Cloud, Cases are migrated as a custom object (Problem__c) with equivalent fields to preserve the data.

Custom fields on Prospect CRM Contacts, Companies, and Deals migrate as Salesforce custom fields. We capture field type (dropdown, date, number, text, checkbox) during discovery and map to the equivalent Salesforce field type. Dropdown fields in Prospect CRM become Picklist or Multi-Select Picklist in Salesforce; date fields become Date; numeric fields become Number with appropriate precision and scale. Validation rule requirements are documented for post-migration configuration by the customer's admin.

Prospect CRM User records (names, email addresses, and role assignments) map to Salesforce User records. We resolve each Prospect CRM user by email against the destination Salesforce org's User table. Any Prospect CRM user without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role assignments map to Salesforce Role hierarchy if applicable.

File attachments on Deals, Contacts, and Problems migrate via URL reference where Prospect CRM exposes a download URL, or the file bytes are uploaded to Salesforce Files (ContentDocument) and linked via ContentDocumentLink to the parent record. We flag any attachment size limits in the target platform and advise splitting large files during re-upload if necessary.

Prospect CRM's deep native integrations with back-office systems (Unleashed, DEAR, TradeGecko, QuickBooks, Xero) are connection-level configuration, not data. These integration links do not migrate. We document every active integration during scoping, capture the required credentials and API endpoints, and deliver a reconnection checklist for re-establishing each connection in Salesforce. This is a manual admin task post-migration.