Migrate from Sentian Solutions to Salesforce Sales Cloud

Sentian company records map directly to Salesforce Account. The Account.Name field receives the company name. If Sentian stores parent-child hierarchies, the Salesforce ParentId field is used to preserve the structure. Circular references are flagged during validation. If the hierarchy depth exceeds Salesforce's limit of five levels, FlitStack AI will flatten the relationship and store the top-level parent in the ParentId field while preserving lineage in a custom hierarchy path field.

Sentian contact records map to Salesforce Contact with AccountId populated by resolving the associated company from Sentian. If the Sentian contact has no company association, a default placeholder Account is created or the contact is flagged for manual assignment before the full migration runs.

Sentian contacts that represent early-stage prospects with no closed-won deal history are split to Salesforce Lead. The split decision is based on Sentian status values—records marked as 'prospect' or 'unqualified' route to Lead; records with active engagement history route to Contact. Your team confirms the split criteria during migration planning.

Sentian deal records map to Salesforce Opportunity. The Opportunity.StageName receives the Sentian deal status value via value-mapping against Salesforce's stage pick-list for the assigned record type. Opportunity.Amount and Opportunity.CloseDate migrate directly from Sentian amount and expected close fields. All monetary values are formatted as Decimal fields, and any currency symbols are stripped during mapping. The CloseDate is stored in the UTC timezone to align with Salesforce's datetime handling.

Sentian pipelines become Salesforce Sales Processes keyed by RecordTypeId. Each Sentian pipeline requires a corresponding Salesforce record type so that stage pick-list values are scoped correctly and page layouts vary per deal category. We deliver a record-type setup plan as part of the migration package.

Sentian stage names are mapped value-by-value to Salesforce Opportunity StageName values under the relevant record type. Stage probability and forecast category are re-applied based on Salesforce's stage configuration. Stage-entry timestamps are preserved in custom datetime fields for historical reporting continuity.

Sentian custom properties attached to standard objects (Account, Contact, Deal) migrate as Salesforce custom fields with the __c suffix. Field-level security must be set per profile after migration. FlitStack creates a custom field manifest and deploys fields before data loads to avoid insertion errors.

Sentian custom objects map 1:1 to Salesforce custom objects. Custom object associations that use many-to-many relationships in Sentian require Salesforce junction objects with two lookup fields. We identify junction requirements during the mapping phase and include them in the schema plan.

Sentian activity logs are decomposed: call and email activities become Salesforce Task records with Type='Call' or Type='Email'. Meetings become Salesforce Event records with original start and end times. Notes, including rich-text formatted notes, migrate to Salesforce Notes (ContentNote) with parent record links preserved via WhatId and WhoId.

Sentian file attachments are downloaded and re-uploaded to Salesforce Files (ContentDocument / ContentVersion model). File size limits apply—Salesforce default caps individual files at 25MB. Files exceeding this threshold are flagged for manual handling or chunked upload before the migration commits.

Sentian user IDs are resolved to Salesforce User records by email address match. Unmatched owners are flagged before migration begins—your team either creates Salesforce user accounts for them or assigns a fallback owner. No record lands in Salesforce without a resolved OwnerId.

Sentian's internal record ID is stored in a Salesforce custom text field (Source_System_ID__c) on each migrated record. This field enables delta-run de-duplication, rollback identification, and traceability back to the original Sentian data for audit purposes. During subsequent data refreshes, FlitStack AI compares Source_System_ID__c values to identify new, changed, or deleted records, ensuring Salesforce stays synchronized with the latest Sentian state without creating duplicates.