Migrate from Sentia to Zoho CRM

Sentia Contact records map directly to Zoho CRM Contacts. We preserve all standard fields (name, email, phone, address) and custom Contact-level properties as custom fields in Zoho. The Contact's associated Sentia Company record is linked via the Account_Name lookup in Zoho, resolved by company name matching before Contact import begins. Custom date fields (such as birthday or contract start) migrate as Zoho Date fields; multi-select custom properties migrate as Zoho Multi-Select Picklist fields.

Sentia Company records map to Zoho CRM Accounts. Company name is the dedupe key; matching is case-insensitive with duplicate Accounts flagged for customer review before insert. Company phone, website, industry, and address fields map to the corresponding Zoho Account fields. Sentia Company-to-Contact associations are preserved as Zoho Contact records linked to the parent Account via Account_Name lookup.

Sentia's Lead object has no direct Zoho CRM equivalent because Zoho uses a Lead module rather than a separate unconverted Lead concept. We offer two strategies during scoping: (1) merge Sentia Leads into Zoho Leads, preserving lead source and lead status as custom fields; (2) merge qualified Sentia Leads directly into Zoho Contacts attached to Accounts. The choice depends on the customer's qualification process and whether they use Zoho's Lead-Contact-Account conversion workflow. We compute the merge rule during scoping and apply it as the first transform before any record import.

Sentia Deals map to Zoho CRM Deals with pipeline stage mapping by name proximity and customer confirmation. Deal amount, expected close date, and probability migrate directly. Closed-won and closed-lost outcomes map to Zoho's Closed Won and Closed Lost stage values. Sentia's pipeline stage change log migrates as Zoho Deal notes or as a custom field tracking last stage change date. We resolve the associated Account (from Sentia Company) and Owner at migration time before Deal insert.

Sentia pipeline stages map to Zoho CRM Stage values by name match. We configure the Zoho Sales Process and picklist values during schema pre-creation so that stage probability percentages migrate from Sentia to Zoho. Any custom stage property such as probability weighting or stage-specific SLA becomes a custom field on the Deal. The customer confirms the mapping table during the scoping call before migration begins.

Sentia Engagement records (calls, emails, meetings, notes, tasks) map to Zoho CRM equivalent objects. Call engagements become Task records with Task_Subtype set to Call and Call_Duration preserved. Email engagements become Task records with a Zoho Email record linked. Meeting engagements become Event records with Start_Time and End_Time preserved. Notes become Note records linked via ContentDocumentLink to the parent Contact, Account, or Deal. All activity timestamps are preserved as the original Sentia creation date, not the migration run date.

Sentia custom fields migrate as Zoho CRM custom fields created during schema pre-creation. We query the Sentia metadata API during discovery to enumerate all available custom fields on the customer's active tier (Basic exposes fewer custom field types than Ultimate). Zoho's 300-field limit per module applies; if the customer's total field count across a module approaches this limit, we flag it during scoping and prioritize the most business-critical fields for migration. Custom field data types are mapped: text to Single-Line, textarea to Multi-Line, date to Date, number to Numeric, checkbox to Checkbox, picklist to Picklist.

Sentia Users who own records are resolved by email match against the Zoho CRM destination User table. Any Sentia Owner without a matching Zoho User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Zoho Users are matched only if the customer specifies that the original Sentia user is inactive and the record ownership should be transferred to a different user.

File attachments associated with Contacts, Deals, or Activities migrate as Zoho CRM Attachments. Files above 25MB are flagged before migration; these require manual upload post-migration or Zoho's Large File Storage add-on. We transfer the file reference URL from Sentia where available and reconstruct the attachment linkage in Zoho during migration. Email attachments associated with Activity records migrate as part of the parent email record.

Sentia record tags migrate as Zoho CRM Tags. Where the customer prefers a structured taxonomy, tags with fewer than 50 distinct values migrate as Zoho Multi-Select Picklist fields on the relevant module. The customer chooses the tag strategy during scoping. Tags with high cardinality (over 50 distinct values) remain as Zoho Tags for flexibility.

Sentia automations, workflow rules, and voice workflow configurations do not have a portable schema and are not migrated. Voice workflow configurations reference internal Sentia record IDs that are not transferable. We deliver a JSON representation of each automation's trigger, conditions, and actions for manual reconfiguration in Zoho CRM. The customer's admin rebuilds these using Zoho's Workflow Rules (condition-triggered), Blueprint (stage-based process enforcement), Assignment Rules, and Deluge scripting for custom logic. This work is outside the data migration scope.