Migrate from Factoreal to Freshsales

Factoreal Contacts map to Freshsales Contact for records that represent active customers or qualified buyers, and to Freshsales Lead for unqualified prospects. We determine the split using Factoreal's contact lifecycle stage property (if present) or source attribution (campaign-sourced contacts go to Lead; direct customer records go to Contact). Each Factoreal contact record carries a unique email that serves as the dedupe key during Freshsales import. Custom fields on Factoreal contact records map to Freshsales Contact custom fields or Lead custom fields depending on the split outcome. Required Freshsales fields (first_name, last_name, email) are validated against the Factoreal export before each batch commits.

Factoreal company records map directly to Freshsales Account. The company domain name from Factoreal becomes the Account Website field and is used as the dedupe key. Account must be created before any Contact or Lead import so that the Account Lookup relationship is satisfied at insert time. Address fields (city, state, country) map to Freshsales Address composite field.

Factoreal Segments define filter rules over contact attributes and behavioral events. We capture the full segment membership at migration time — the set of contact IDs belonging to each segment — and reconstruct that membership in Freshsales as a Static List (explicit record membership) or as a Saved Filter that reproduces the same filter logic. Segment names map to Freshsales list or filter names. Note that segment filter logic is not portable as executable rules; we document the filter conditions so the admin can configure equivalent filters in Freshsales after migration.

Factoreal campaigns hold subject lines, content, send history, and engagement metrics. We map campaign structure to Freshsales Campaign, preserving campaign name, status, start and end dates, and budgeted cost if present in the export. Engagement metrics (open rate, click rate, send volume) are stored as custom numeric fields on the Freshsales Campaign record. Freshsales Campaign objects do not support multi-channel execution the way Factoreal campaigns do; channel-level messaging (SMS, WhatsApp) migrates separately as conversation history.

Factoreal's built-in e-commerce integration captures order and product data. We map Factoreal product records to Freshsales Product2 (with SKU preserved in the Product Code field) and create Standard Price Book entries during migration. Factoreal order headers map to Freshsales Deals, with deal name derived from order ID and deal amount from the order total. Factoreal order line items map to Freshsales OpportunityLineItem linked to the parent Deal and PricebookEntry. The customer determines the pipeline and stage assignment for migrated deals during scoping.

Channel-level message logs (SMS, WhatsApp) export from Factoreal as part of the contact and campaign data. We preserve send timestamp, direction (inbound/outbound), channel type, and message content. Freshsales stores these records via the Conversations API as part of its chat module. Each conversation is linked to the corresponding Contact or Lead record by email match. Note that Freshsales chat must be provisioned on the destination account before conversation records can be created via API.

Factoreal email templates include HTML content and dynamic merge field placeholders. We extract template HTML from the export and map merge field syntax to Freshsales template variable format ({{contact.first_name}} becomes the equivalent Freshsales placeholder). Visual template elements render differently across platforms; we preserve the content and variable structure, but the customer reviews template rendering in Freshsales after migration. Static assets (images hosted on Factoreal's CDN) may need to be re-hosted or uploaded to Freshsales's asset library.

Factoreal custom fields on contact and company records are identified during discovery, exported per record, and mapped to Freshsales custom fields of the equivalent type (text, number, date, picklist, checkbox, phone, URL). Freshsales supports custom fields on Lead, Contact, Account, Deal, and Custom Objects. Custom field definitions are created in Freshsales Admin settings before record import. Freshsales Lead-to-Contact field mapping during lead conversion is handled separately in Admin settings; we document the intended mapping during scoping for the customer's admin to configure post-migration.

Factoreal contacts carry multiple tags defining segmentation and classification. We export the full tag list per contact and create equivalent tags in Freshsales using the Tags API or Admin interface. Tags on Freshsales Contact or Lead records use the native tagging feature. The many-to-many relationship between contacts and tags is preserved across both systems.

Factoreal automation workflows define trigger conditions and multi-step action sequences across channels. We do not migrate automations as executable rules because they are not stored in an exportable, portable format. We capture the workflow graph — triggers, conditions, delays, action steps, and channel assignments — as a written inventory document. The customer's admin uses this document to rebuild equivalent logic in Freshsales Workflow Builder (available from Pro tier). Automations that reference channels not available in Freshsales (e.g., Factoreal-specific WhatsApp session templates) are flagged with a recommendation for Freshsales's built-in chat channels.