Migrate from Sentia to Salesforce Sales Cloud

Sentia Contacts migrate directly to Salesforce Contact. Standard fields (Name, Email, Phone, Title, Address) map by API name. We preserve any custom Contact-level properties as typed custom fields (with __c suffix) that we pre-create in Salesforce during schema design. The mapping handles name parsing where Sentia stores a full name string and Salesforce expects separate FirstName and LastName fields.

Sentia Company records map to Salesforce Account. Company name becomes Account Name; domain becomes Website. The Contact-to-Company association migrates as Account-Contact lookups. We run case-insensitive deduplication on Account names during import and flag duplicates for customer confirmation before insert.

Sentia Lead records migrate to Salesforce Lead. Lead source and lead status from Sentia map to Salesforce LeadSource and LeadStatus respectively. Any custom lead scoring or qualification fields become custom fields on the Salesforce Lead object. Leads without a matching Salesforce User owner are held in a reconciliation queue for admin provisioning before the migration phase.

Sentia Deals map to Salesforce Opportunity. The deal name becomes Opportunity Name; monetary value becomes Amount; pipeline stage maps to StageName. CloseDate migrates directly. We pre-create the Salesforce Sales Process that mirrors the Sentia pipeline stages with matching probability percentages before migration begins.

Each Sentia pipeline stage becomes a Salesforce Opportunity StageName value within a Sales Process we configure during schema design. Stage probability percentages migrate from Sentia to StageProbability on each Opportunity record. Custom stage properties such as probability weighting and stage-specific actions are documented in the handoff inventory for Salesforce admin rebuild in Flow.

Sentia call activities map to Salesforce Task with TaskSubtype = Call. Call duration, disposition, and any recording URL preserved as custom Task fields. ActivityDate reflects the original Sentia timestamp to maintain timeline ordering. WhoId on the Task resolves to the migrated Contact or Lead; WhatId resolves to the related Opportunity or Account.

Sentia email activities migrate to Salesforce EmailMessage records (the content) linked to a Task record (the activity timeline entry). The email direction (inbound/outbound) maps to EmailMessage direction. HasAttachment and AttachmentIds preserve file references. WhoId and WhatId resolve to the parent Contact or Account at migration time.

Sentia meeting activities map to Salesforce Event. StartDateTime, EndDateTime, and Location migrate directly. Attendee records create EventRelation entries linked to the attending Contacts, Leads, and Users. We set the IsAllDayEvent flag based on whether the Sentia meeting has a duration of zero.

Sentia notes attached to Contacts, Deals, or Companies migrate to Salesforce Note records linked via ContentDocumentLink to the parent record. Note body migrates as plain text; any embedded attachments become separate ContentDocument records. We preserve the original creation timestamp on each Note for audit.

Custom fields on Sentia Contacts, Companies, Leads, and Deals migrate to typed Salesforce custom fields. We discover the full field schema via the metadata API during discovery, filtering to fields available on the customer's active Sentia tier (Basic, Starter, or Ultimate). Field types are mapped to nearest Salesforce equivalents: picklist to picklist, multi-select to multi-select picklist, date to date, number to number. Any fields unavailable on the Basic tier are flagged before migration begins.

Sentia Users referenced as record owners map to Salesforce User by email match. We build a user-mapping table during scoping and validate every owner reference against the destination org's User table. Any Sentia User without a matching Salesforce User enters a reconciliation queue for admin provisioning. OwnerId assignment on Contacts, Accounts, Opportunities, and Leads cannot proceed until all owner references are resolved.

File attachments associated with Contacts, Deals, or Activities migrate as Salesforce ContentDocument records linked via ContentDocumentLink to the parent record. Files above 25MB are flagged for alternative transfer (SFTP drop or signed URL) because the Bulk API 2.0 has attachment size limits. We preserve the original file name, content type, and creation timestamp.