Migrate your Sentia data

Contacts are the primary person records in Sentia with automatic data capture on the Starter tier. We migrate Contacts with all standard fields and preserve any custom Contact-level properties as mapped custom fields. Email, phone, and address data is handled with format normalization during import.

Company/Account records hold organizational data linked to Contacts. We preserve the Contact-to-Company association during migration. Company names are matched case-insensitively and duplicates are flagged for customer review before final import.

Leads are distinct from Contacts in Sentia's data model. Where the destination CRM does not have a separate Lead object, we merge Leads into Contacts and preserve the lead source and status as custom Contact properties. Lead assignment to Users requires re-mapping to destination User IDs.

Deals represent opportunities with associated pipeline stages and monetary values. We map Deal records with their pipeline stage history preserved as a staged-change log on each record. Closed-won and closed-lost statuses are migrated as-is and are not reactivated.

Pipeline stages are customizable per organization. We map source stages to destination stages by name proximity with customer confirmation required. Custom stage properties such as probability percentages are migrated as custom numeric fields on the Deal object if the destination schema supports them.

Custom fields are available on both Basic ($10/mo) and Ultimate ($30/mo) tiers but the Ultimate tier exposes more field types and API-accessible properties. We discover the full field schema via the metadata API before field mapping and flag any fields not available on the customer's active tier.

Activities include calls, emails, meetings, and notes attached to Contacts or Deals. We migrate activity records with timestamps, content, and owner attribution. Activity-to-Contact associations are preserved; activity-to-Deal associations require verification against the destination's activity-linking model.

Users are the internal reps and admins who own records. Owner assignment at migration time requires a user-mapping table because Sentia User IDs are not transferable to the destination. We ask customers to provide the mapping before the import run and fall back to a migration-in-progress user for unmapped records.

File attachments associated with Contacts, Deals, or Activities are migrated via file reference or re-upload depending on the destination's attachment handling. Large attachments above 25MB are flagged for manual handling since some platforms store these separately from the CRM record.

Sentia supports tagging records for segmentation. Tags are migrated as label arrays on the target object. Where the destination uses a different tagging taxonomy, we map tags to the nearest equivalent label and document any that cannot be directly migrated.

Automations, workflow rules, and voice workflow configurations are platform-specific logic that does not have a portable schema. We export a JSON representation of the automation rules for manual reconfiguration in the destination CRM. No automation data is imported automatically.