Migrate from Sentian Solutions to Zoho CRM

Sentian contacts map to Zoho Leads by default. If a Sentian contact record carries a 'status' or 'type' property indicating a closedwon or active customer, those records split to Zoho Contacts instead. The split rule is configurable per your business logic and verified in the sample migration before the full run.

Sentian company records map 1:1 to Zoho Accounts. Zoho requires Account_Name (display) for every account record. If a Sentian company record has no name, we use the primary domain or a placeholder and flag the record for your admin to clean up post-migration.

Sentian parent-child company relationships map to Zoho Account.ParentId. Parent accounts must migrate first; we sequence the migration so child accounts reference an already-existing parent. Circular references (A is parent of B, B is parent of A) are flagged and resolved before the account import runs.

Sentian deals map to Zoho Deals as a direct object mapping. Deal amounts, names, close dates, and owner assignments transfer directly. Zoho Deals store the associated account as an Account_Name lookup — the account must already exist, so accounts migrate before deals.

Sentian deal stage names do not automatically match Zoho's default stage picklist values. We map each Sentian stage name to the corresponding Zoho pipeline stage by value, creating new stages in Zoho if no match exists. Stage probability and forecast category are preserved as custom fields on the Deal record for reporting continuity.

Sentian tasks map to Zoho Tasks with subject, description, status, priority, due date, and the parent record lookup preserved. Original create timestamps are stored in a custom datetime field (Original_Create_Date__c) since Zoho's CreatedTime is set at migration time. Unlinked tasks (no parent record) migrate as standalone tasks.

Sentian events map to Zoho Events, preserving start datetime, end datetime, all-day flag, location, and the parent record lookup. Recurring events in Sentian are flattened into individual Zoho event records using the original recurrence rule as a custom text field — recurring automation is not rebuilt automatically.

Sentian notes map to Zoho Notes. Zoho Notes are a standalone module — each note tracks a parent record (Contact, Account, or Deal) via a lookup field. We populate the parent lookup during migration so notes appear in context on the source record's detail page. Zoho Notes do not support upsert; post-migration edits in Zoho are not reflected back in Sentian.

Sentian file attachments on records are downloaded and re-uploaded to Zoho Attachments. Zoho enforces a per-file size limit (default 25MB); files exceeding the limit are flagged and your admin decides whether to split or skip. Inline images embedded in notes are extracted and rehosted as separate attachments.

Sentian custom fields require pre-creation in Zoho before data can migrate into them. We create each custom field via the Zoho CRM Field API (/crm/v8/settings/fields) using the matching data type (text, picklist, multi-select, checkbox, date, etc.). For picklist and multi-select fields, we pre-populate the Zoho picklist values with Sentian's options before the import phase.

Sentian owner IDs are resolved to Zoho users by email address match. Before migration, we pull your Zoho user list via the Users API and create a mapping table. Any Sentian owner whose email has no matching Zoho user is flagged — your admin either creates the Zoho user first or assigns those records to a fallback owner before migration begins.

Sentian product or line-item records map to Zoho Products. Unit price, product code, quantity available, and product description transfer directly. If Sentian stores product images, those are re-uploaded as Zoho product attachments. We also map product categories and custom product fields to Zoho's custom product attributes. For items with multiple pricing tiers, each tier can be entered as a separate product or linked via Zoho's price book.

Sentian record tags transfer as Zoho Tags. Zoho Tags are supported on most standard modules and appear as filterable chips on record list views. Tag creation is automatic — if a Sentian tag does not yet exist in Zoho, FlitStack creates it during migration.