Migrate from Sellsation CRM to Freshsales

Sellsation Customers map to Freshsales Accounts with address, industry, and company metadata preserved as standard Account fields. Any Sellsation custom fields on Customer records migrate as Freshsales custom properties on Account. Company-level notes and tags export as Freshsales Account notes attached to the Account record.

Sellsation Contact Persons map to Freshsales Contacts with the parent Account resolved by Customer name match. Phone, email, job title, and custom properties migrate directly. Sellsation's traffic-light neglect flag (stagnation status) translates to a custom Contact field for sales manager visibility in Freshsales.

Sellsation Sales Projects map to Freshsales Deals with pipeline stage, deal value, and phase change history preserved. Sellsation pipeline stage names map to Freshsales deal stages via a migration-time lookup table. The stagnation flag (traffic-light system) translates to a Freshsales custom field on Deal. Deal-to-Contact and Deal-to-Account lookups resolve at migration time using the Customer and Contact Person parent relationships.

Sellsation's unified Activity record type splits into Freshsales native objects by engagement type: calls and tasks become Tasks, appointments become Appointments, and standalone notes become Notes. We preserve the original timestamp, assigned user, and parent linkage (Contact or Deal) for each activity record. Activity volume in active Sellsation accounts can be 10–20 times the contact count, so we chunk exports into time-bounded batches to prevent file-size issues.

Sellsation Tasks map directly to Freshsales Tasks with status, priority, due date, and assigned user preserved. The parent linkage (Contact Person or Sales Project) resolves to Freshsales Contact or Deal at migration time via the Customer and Contact Person name matching step.

Sellsation Appointments map to Freshsales Appointments with date, time, duration, location, and attendee list preserved. Attendees link to Freshsales Contact records via email matching. Any appointment notes migrate as a Freshsales Note attached to the Appointment record.

Sellsation multi-level campaigns combine emails, letters, conditional stage movements, and automated task creation. Freshsales does not have a campaign object with the same multi-level structure. We export campaign enrollment data, member lists, and campaign status as a CSV that the customer's Freshsales admin imports as a target list or segment. The automation logic requires rebuild as Freshsales workflow rules on Pro or Enterprise tiers; we document the original campaign logic for admin reference.

Sellsation custom fields on Customers, Contact Persons, and Sales Projects map to Freshsales custom properties on Account, Contact, and Deal. We enumerate all custom fields during scoping, identify their data type (text, number, date, picklist), and create matching Freshsales custom properties before migration. Picklist-dependent fields require Freshsales admin to pre-create the picklist values; we flag these during scoping.

Sellsation territory heatmap and candidate location data stores as proprietary map state rather than standard coordinates. We extract the linked Sales Project location as standard address fields (street, city, country) and store a geo flag in a custom field. The native heatmap visualization cannot be replicated in Freshsales; the address data provides geographic context for territory reporting.

Sellsation report definitions and dashboard configurations do not export. We migrate the underlying data—Sales Project values, activity counts, pipeline stage history—so the Freshsales admin rebuilds reports from complete source data. The KPI measurement data from Sellsation Salesleader migrates as a time-series dataset attached to Deals for pipeline analytics.