Migrate from Sentia to Freshsales

Sentia Contact records map directly to Freshsales Contact. Standard fields (name, email, phone, address) transfer via field-level mapping. Custom Contact-level properties migrate as Freshsales custom fields that we pre-create before the import phase. The Contact record is the primary person entity in both platforms with a 1:1 correspondence at the object level, requiring no structural split.

Sentia Lead records migrate to Freshsales Lead with the Sentia lead source preserved in a custom field (e.g., sentia_lead_source__c) and the original lead status mapped to Freshsales Lead Status. After migration, Freshsales admins run the Lead Convert action to create Contact and Account records from each Lead. We flag any Freshsales plan limits on Lead record counts and advise customers to confirm their plan's Lead storage allowance before migration.

Sentia Company records map to Freshsales Account. The Company name becomes the Account name, and domain data maps to the Website field. We use Account name as the dedupe key and resolve any case-insensitive duplicates before insert. Company-to-Contact associations migrate via the Freshsales Account-Contact link, which we resolve after both objects are loaded.

Sentia Deal records map to Freshsales Deal. The pipeline stage from Sentia maps to Freshsales Deal stage with customer-confirmed name matching. Deal amount, close date, probability (if custom-defined), and owner migrate directly. Closed-won and closed-lost states transfer as Freshsales Deal status values. We preserve Sentia's deal stage change history as a note on the Freshsales Deal if the source exposes that log.

Sentia pipeline stages are organization-specific and customizable. We map source stage names to Freshsales stage names by exact or proximity match with customer confirmation required for any ambiguous mapping. Stage probability percentages migrate as Freshsales stage probability values. Freshsales allows custom stage creation in Admin Settings before migration, so we coordinate stage provisioning as a pre-migration configuration step.

Sentia activities attached to Contacts or Deals migrate as Freshsales Activity records with the activity type (call, email, meeting, note) preserved. Timestamps transfer to the Activity date fields. Activity content (body, subject) migrates as plain text. We resolve the parent Contact or Deal reference at migration time using the Freshsales API to locate the target record by email or name match.

Sentia Users who own records require a mapping table because Sentia User IDs do not transfer to Freshsales. We extract all distinct owner emails from the source records and match against the Freshsales User table by email. Any Sentia owner without a matching Freshsales User goes to a reconciliation queue; the Freshsales admin provisions the missing User before record import resumes. Inactive Sentia owners map to inactive Freshsales Users to preserve historical attribution.

Custom fields migrate as Freshsales custom fields that we pre-create in the Admin Settings before the migration run. Critical constraint: the active Sentia tier determines API access to custom field data. We audit the metadata API during discovery to identify all available custom fields on the customer's tier. Basic tier ($10/month) customers may have fewer exposed custom fields than Starter or Ultimate; we flag any unavailable fields and advise the customer before migration begins.

Sentia tags migrate as Freshsales tags on the equivalent object (Contact tag, Account tag, Deal tag). Tags that represent lead segmentation migrate to Freshsales Lead tags. We use a tag name match with case normalization. If the customer uses a tagging taxonomy in Sentia that they want to restructure in Freshsales, we apply the remapping during the transform phase before import.

File attachments associated with Contacts, Deals, or Activities migrate via file reference re-upload. We extract the attachment binary and upload to Freshsales via the Files API, then link the file to the parent record. Attachments above 25MB are flagged as requiring manual upload or an alternative file hosting reference. Email attachments embedded in activity content migrate as part of the activity body text.