Migrate from Systeme IO to Freshsales

Systeme.io contacts with no associated deal or a deal in early stage map directly to Freshsales Contact records. The email address serves as the unique identifier, and core fields such as phone, job title, city, state, and country map field-for-field into Freshsales' standard Contact object. If a contact carries custom field values, those are written to the corresponding custom fields after they have been pre-created in Freshsales by an admin.

Systeme.io contacts who have a deal associated with them and are not yet confirmed customers route to Freshsales Lead records. This split reflects Freshsales' distinction between a Lead (unqualified prospect) and a Contact (qualified buyer with an established relationship). After migration, the sales team runs standard lead conversion to create Account and Contact records.

Systeme.io company records map 1:1 to Freshsales Account records. Company name, domain/website, industry, number of employees, and annual revenue map to Freshsales' standard Account fields. Multi-company associations on a single contact in Systeme.io collapse to one primary Account in Freshsales.

Systeme.io deals map to Freshsales Opportunity records. Each deal name becomes an Opportunity name, deal amount maps to Amount, close date maps to Expected Close, and deal owner email resolves to a Freshsales user OwnerId. Stage mapping is value-based per pipeline (see Pipeline Stage mapping).

Systeme.io pipelines become Freshsales Sales Pipelines. Each pipeline in Systeme.io gets its own named pipeline in Freshsales. Pipeline stage names and their relative order are preserved, but stage probability and forecast category are set based on Freshsales' default stage values per pipeline.

Stage names map value-by-value from Systeme.io to Freshsales per pipeline. For example, Systeme.io's 'Qualification' stage maps to Freshsales' 'Qualification' stage within the corresponding pipeline. If Systeme.io has a stage name not present in Freshsales, the stage is created as a custom stage in that pipeline before migration.

Systeme.io tags on contacts and deals migrate as Freshsales tags. Freshsales supports tagging on Leads, Contacts, Accounts, and Opportunities. Tags preserve segmentation and campaign attribution from Systeme.io. Tags that exceed Freshsales' character limits are truncated at the limit (64 characters per tag).

Systeme.io custom contact fields that have no direct Freshsales equivalent are created as custom fields on the target object (Contact or Lead). Field type is mapped: text fields become Short Text, number fields become Number, date fields become Date. The custom field is created in Freshsales before migration data loads.

Systeme.io custom deal fields migrate to Freshsales custom fields on the Opportunity object. Field type mapping follows the same rules as contact custom fields. Custom fields on deals that are informational only (not used in reporting) can optionally be stored as a JSON-formatted text field for reference.

Systeme.io email history logged against a contact migrates as Freshsales Sales Activities. Each email appears as a Sales Activity record linked to the contact. The email subject, body preview, and timestamp are preserved. Full email body content migrates if it does not exceed Freshsales' character limit per activity note.

Systeme.io owner records are resolved by email address against Freshsales user accounts. Any Systeme.io owner email that does not match a Freshsales user is flagged before migration. The client either creates the missing user in Freshsales or designates a fallback user to own those records in the destination.

Systeme.io's original created_at and updated_at timestamps are preserved as custom datetime fields in Freshsales (Original_Created_Date__c, Original_Updated_Date__c) because Freshsales sets its own Created At at data load time. Keeping the original creation and modification dates allows reports to reflect the true lifecycle of each record, maintain historical trend analysis, and meet audit requirements. These fields appear on Lead, Contact, Account, and Opportunity records as custom attributes for post‑migration reference.