Migrate from Sentian Solutions to Freshsales

Sentian entities that represent people or organizational contacts map directly to Freshsales Contact records. FlitStack resolves the primary organization link from Sentian's entity-to-organization relationship and creates the Contact.AccountId lookup automatically. All standard contact fields including name, email address, phone number, and job title migrate directly without transformation. This mapping applies to any Sentian entity classified as a person-type record.

Sentian entities that represent unqualified prospects or early-stage records map to Freshsales Lead. The mapping uses Sentian's entity type classification or lifecycle indicator to route records correctly into the Lead object. FlitStack preserves Sentian lead status as a custom field if no direct StageName match exists in Freshsales' default lead status pick-list.

Sentian organization entities map to Freshsales Account records. Company name becomes Account Name, domain maps to Website field, and industry and employee count fields migrate directly without transformation. Parent-child organization hierarchies in Sentian translate to Freshsales Parent AccountId lookup when the parent organization also migrates — parent accounts must be sequenced before their child records.

Sentian entities that represent sales opportunities or tracked deals map to Freshsales Deal records. Deal name, value, close date, and stage all have direct Freshsales counterparts. Sentian's deal stage names are mapped via value-mapping to Freshsales Deal Stage pick-list values during migration to ensure pipeline continuity.

Sentian events and alerts that represent sales-relevant activities such as calls, meetings, and follow-up tasks map to Freshsales Task or Event based on type classification. Alert timestamps become Task CreatedDate or Event StartDate. Non-activity alerts like system notifications are excluded from migration as they have no Freshsales equivalent object.

Sentian call logs and email activity records map to Freshsales Sales Activities with original timestamps, duration, and outcome notes fully preserved during migration. The activity record is linked to the parent Contact or Lead record using Freshsales' association model to maintain the complete relationship chain between activities and their related contacts.

Sentian custom entity types that exist in lower-tier Freshsales plans without custom module support are decomposed: custom fields are created on the closest standard object (Contact, Account, or Deal), and the custom entity name is preserved as the field label. Freshsales Enterprise can receive custom entity types as full custom modules via the app SDK for complete schema preservation.

Sentian file attachments associated with entities are re-uploaded to Freshsales Files attached to the corresponding Contact, Account, or Deal record. Freshsales file size limits apply (25MB default per file). Inline images embedded in notes are extracted and re-hosted as separate file attachments to maintain visual content accessibility.

Owner resolution maps Sentian user email addresses to Freshsales user email addresses to maintain assignment continuity. Records with unmatched owners are flagged before migration commits. Unmatched records are assigned to a designated fallback owner specified during migration planning. This owner resolution step is the most common pre-migration blocker and is addressed comprehensively in the discovery phase.

Sentian alert rules and notification automations have no direct Freshsales equivalent and therefore cannot be migrated automatically. FlitStack exports Sentian workflow definitions as a structured JSON reference document capturing trigger conditions, action logic, and target entities. Your Freshsales administrator can use this export as a rebuilding guide when creating equivalent automations in Freshsales' native Workflow builder application.

Sentian entities with many-to-many relationships to other entities are decomposed during migration: the primary relationship becomes a direct lookup such as Contact.AccountId, and additional relationships are surfaced via Freshsales' Contact-Account relationship model or a custom association field if the relationship type is non-standard and requires custom handling.

Sentian's created_date, modified_date, and any entity-specific audit timestamps are preserved as custom datetime fields on Freshsales records such as Original_Create_Date__c and Source_Last_Modified__c. Because Freshsales system timestamps are set at migration time rather than reflecting source record history, FlitStack preserves the original values in custom fields to maintain audit continuity and historical reporting accuracy.