Migrate from Simplero to Freshsales

Simplero Contacts map to Freshsales Lead for unqualified prospects and Contact for qualified contacts. We apply a split rule based on the customer's data: contacts with active enrollments, purchases, or recent engagement activity become Freshsales Contacts attached to Accounts; all others become Leads. Tags and segment assignments migrate as multi-select picklist custom fields on both Lead and Contact. Custom Contact Fields require pre-creation in Freshsales Admin Settings before import. The subscription opt-in status from Simplero maps to Freshsales HasOptedOutOfEmail on the Contact record.

Simplero Products (courses, memberships, digital downloads, coaching programs, sessions) map directly to Freshsales Product2 records. Product pricing, product-type classification, and access rules migrate as custom fields on Product2. Note that Freshsales Product2 does not natively track course access rules or membership tiers—these require custom fields or a separate custom module on the Enterprise plan.

Simplero Deals (available on Skyrocket tier) map to Freshsales Deals. Deal stage, value, owner, and close date migrate directly. Pipeline stage names from Simplero become Freshsales Deal stage values, configured in Freshsales Admin Settings before migration. Closed-Lost and Closed-Won statuses map to Freshsales standard deal statuses. Simplero Deals without a pipeline assignment become Freshsales Deals in the default pipeline.

Simplero Orders (product, price, date, payment gateway, refund status) require transformation because Freshsales does not have a native Order or subscription object. We map each Order to a Freshsales Deal with line items referencing the mapped Product2, and refund status and payment gateway stored as custom fields on the Deal. Complex subscription histories with recurring billing may require a custom module on Freshsales Enterprise.

Simplero Members with active product access do not map cleanly to any standard Freshsales object. On Freshsales Enterprise, we create a custom module (up to 630 fields across 20 custom modules) to store enrollment records with the contact lookup, product lookup, enrollment date, and expiration. On lower tiers, enrollment data migrates as Note records attached to the Contact for audit and reference. The customer chooses the strategy during scoping based on their Freshsales plan tier.

Simplero Automation Flows are not accessible via API or any export mechanism at any tier. We do not migrate Flow logic. During discovery we document the Flow structure—trigger events, step sequence, conditions, and actions—using Simplero's UI exports and screenshots. This Flow inventory document is handed off to the customer for manual rebuild in Freshsales Workflows. This is a significant manual effort for complex sequences and should be budgeted separately.

Simplero help desk tickets (available on Scale and Skyrocket) map to Freshsales Case if the destination Freshsales account includes Service Cloud features. Ticket subject, status, assignee, and conversation thread migrate. Conversation threads migrate as EmailMessage records linked to the Case. Note that Freshsales base CRM does not include Service Cloud; Cases require the customer to have the appropriate Freshsales plan with Service Cloud enabled.

Simplero tags and segment assignments are flat key-value labels and dynamic filter groups attached to contacts. We preserve them as Freshsales multi-select picklist custom fields on the Lead and Contact objects. Segment membership for dynamic segments is captured at migration time as static tag values. The customer defines which tags become visible custom fields and which are archived during scoping. The maximum picklist values in Freshsales (300 per field) accommodates most Simplero tag sets.

Simplero blog posts importable via WordPress XML/RSS format. We export the blog as RSS XML and note that Freshsales does not have a native blog or content management object. Post titles, content, slugs, and publish dates migrate as Note records attached to the relevant Contact or Account for reference. Media assets and images are linked as URL references in the Note body rather than embedded. URL slugs are preserved in the Note for the customer's redirect planning.

Simplero site pages and structural content migrate as Note records with the page title, slug, and URL preserved for the customer's redirect planning. Media assets, theme settings, and no-code builder elements do not transfer to Freshsales because Freshsales is a CRM, not a website platform. We deliver a URL redirect map so the customer can configure 301 redirects in their DNS or hosting layer to maintain SEO equity after migration.