Migrate from Prospect CRM to Freshsales

Prospect CRM Contact records with standard fields (first_name, last_name, email, phone, address) map directly to Freshsales Contact. Custom contact properties migrate as Freshsales custom fields. RFM segment assignments (Prospect CRM's Recency, Frequency, Monetary classifications) export as a multi-select or text property on Contact so the customer can maintain segmentation context in Freshsales without rebuilding the model manually.

Prospect CRM Company records map to Freshsales Account. The Company name becomes the Account Name field, and any associated website and industry fields migrate as typed Account properties. We create Accounts before Contact import to satisfy the Account lookup on Contact records, maintaining the Company-to-Contact relationship throughout migration.

Prospect CRM Deals map to Freshsales Deals with pipeline stage name mapping handled explicitly because stage IDs are not portable across platforms. We capture the stage order, stage name, and probability percentage from Prospect CRM and configure matching Freshsales Deal stages before migration. Deal values, owner assignments, and expected close dates migrate directly. Any stock-awareness notes attached to the Deal (e.g., Awaiting Stock status) migrate as a Deal note for the admin to reconcile post-migration.

Prospect CRM Product catalog records (SKU, pricing, description) migrate to Freshsales Products. The stock-aware flag and live inventory linkage do not transfer because Freshsales does not have native inventory integration. We document the original stock-level data as a custom product field (e.g., last_confirmed_stock__c) so the customer can reference it in reporting or re-integration planning.

Prospect CRM's Problem Pipelines (used for delivery issues, returns, and complaints) is a non-standard CRM object with no direct Freshsales equivalent. We extract all Problem records with their Status, Outcome, linked Customer, and description fields, then map them to Freshsales Tickets. We configure the Ticket fields and any relevant Ticket categories during migration setup so that historical customer service records are preserved and queryable post-migration.

Prospect CRM Activity history including calls, emails, meetings, and tasks migrates as chronological Freshsales Activity records. Activity type labels may differ between platforms (e.g., Prospect CRM call dispositions vs Freshsales call outcomes); we map them to the closest equivalent and flag any untranslated activity types in the migration report for admin review.

Prospect CRM's RFM customer segmentation (Recency, Frequency, Monetary value) is stored as platform-specific classification data. We export RFM segment assignments per Contact and load them as a text or multi-select custom field in Freshsales (e.g., rfm_segment__c with values like 'Champion', 'At Risk', 'Lost Customer'). The customer can use this for targeted follow-up campaigns in Freshsales without rebuilding the segmentation model from scratch.

Custom fields on Prospect CRM Contacts, Companies, and Deals migrate as Freshsales custom fields. We capture field type (dropdown, date, number, text) during scoping to ensure validation rules are set correctly post-import. Dropdown fields with specific option sets require manual re-creation in Freshsales with the same value list since import does not replicate picklist metadata.

Prospect CRM User records (names, email addresses, role assignments) map to Freshsales Users. We resolve owners by email match against the Freshsales User table. Any Prospect CRM User without a matching Freshsales User goes to a reconciliation queue for the admin to provision before record import resumes.

File attachments on Deals, Contacts, and Problems migrate as Freshsales attachments linked to the parent record. We flag any attachment size limits in Freshsales during scoping and note that very large files may require chunked re-upload. The original attachment URL reference from Prospect CRM is documented in the migration log for audit purposes.