Migrate from SalesPro CRM to Freshsales

SalesPro Contact records map directly to Freshsales Contact. Email, phone, company association, address, and custom fields transfer as typed fields. Owner assignment resolves via email lookup to the Freshsales User table. Any contacts without an email receive a placeholder email address to satisfy Freshsales uniqueness constraints and are flagged in the reconciliation report for admin review.

SalesPro Company records map to Freshsales Account. The company name becomes the Account Name; any domain or website field maps to the Account's website field. Account is created before Contact import so the Contact-to-Account lookup is satisfied at insert time. If duplicate company names exist in SalesPro, we merge them under a single Account and flag the merge in the reconciliation report.

SalesPro Event records map to Freshsales Appointments with start time, end time, location, and description preserved. The event owner maps via email to the Freshsales User. Event-to-Contact linkage is preserved as a Freshsales Appointment contact association. If the SalesPro event contains BEO references, we flag the BEO for custom object reconstruction and maintain the Event-BEO relationship in the Freshsales target schema.

BEO records are derived from Events in SalesPro and contain cost calculations, timeline details, and event specifications. Freshsales has no native BEO object, so we create a custom object named BEO via Freshsales Object Builder with fields for event_date__c, event_group_size__c, cost_estimate__c, timeline_spec__c, and a lookup to the mapped Event. We preserve the Event-to-BEO linkage explicitly as a lookup field rather than relying on naming conventions. If a source Event is deleted before export, its BEO becomes orphaned and we flag it during pre-migration audit.

SalesPro Deals map to Freshsales Deals with deal name, amount, stage, and close date transferred. SalesPro pipeline stages map to Freshsales pipeline stages by name and relative ordering. Probability percentages migrate as deal_score__c or are embedded in the stage name if Freshsales does not expose a separate probability field in the current plan tier. We create the Freshsales pipeline and stage configuration before deal import begins.

SalesPro custom milestone definitions tied to sales cycles or goals map to Freshsales custom fields on the Deal object. Milestone names become field labels; completion status becomes field values. If milestone definitions are numerous or highly customized, we map them as a JSON-encoded custom field milestones__c with structured key-value pairs, preserving all original milestone names and statuses for audit.

SalesPro task records map to Freshsales Tasks with assignees (resolved by email), due dates, email reminder flags, and completion status preserved. Task title and description transfer as typed fields. The original SalesPro task creation timestamp maps to a custom field original_created_date__c for audit.

SalesPro users referenced on Contacts, Events, Tasks, and Deals resolve by email address to Freshsales User records. We request the customer to pre-create Freshsales User accounts matching the SalesPro user emails before migration begins. Any SalesPro user without a matching Freshworks account enters a reconciliation queue and their records are assigned to the migration admin user with an owner_reconciliation flag for post-migration reassignment.

SalesPro calendar entries export as Events with start/end timestamps and resource assignments. We map these to Freshsales Appointments, preserving the resource booking details in a custom field resource_notes__c since Freshsales Appointments do not have a native resource assignment object. The calendar entry-to-contact linkage is preserved via the Freshsales Appointment contact association.

SalesPro does not expose a bulk attachment export endpoint via its webhook API. Attachments associated with Events, Contacts, or BEOs cannot be programmatically retrieved without direct database access. We notify customers during scoping that attachments will not migrate and provide a manual export checklist for the customer to retrieve files directly from SalesPro before account deactivation. We do not skip attachment import by choice; the API constraint is structural.