Migrate from Unim to Zoho CRM

Unim's Contact entity maps to Zoho CRM Contact. We introspect the Contact ModelID and active custom fields from Unim's custom-fields API before building the import map. Standard fields (Name, Email, Phone, Address) map directly. Custom fields are created as Zoho custom fields in the Contact module before migration begins, using DataType lookups from Unim's valuelists endpoint to resolve field types. Contacts are imported after Accounts to satisfy the Account Name lookup.

Unim Company records map to Zoho CRM Account. Company Name becomes Account Name; domain-related fields map to Website. Custom fields on Company resolve through the same DataType lookup process as Contact. Account is created first so that Account lookup fields on Contact are satisfied at the moment of Contact insert.

Unim Activity records (calls, emails, notes, meetings) map to Zoho CRM Task and Event objects. Activity subtype determines the destination: calls become Task with TaskSubtype=Call; notes become Note; emails become Task with type=Email. Meeting-type activities become Event with StartDateTime and EndDateTime preserved. Activity-to-contact and activity-to-company linkages are preserved as WhoId and WhatId on the Zoho record.

Unim custom fields exist per-entity and carry a Name, ModelID, DataType, and Nullable flag. DataType is resolved via the valuelists endpoint before field creation in Zoho. Text fields map to Zoho Text; numeric fields map to Zoho Currency, Number, or Decimal depending on precision; date fields map to Zoho Date; picklist-style fields map to Zoho Picklist. We create all custom fields in Zoho before any record import to avoid silent data loss from unmapped fields.

Unim applications may include bespoke entity types beyond Contacts, Companies, and Activities. We discover these via schema introspection and create corresponding Zoho CRM Custom Modules (with _C naming convention) before migration. Lookup relationships between bespoke objects and standard entities are preserved as Zoho Lookup fields. Multi-level hierarchies map to Zoho's parent-account or hierarchical lookup model.

Unim Owner IDs are instance-scoped and cannot transfer directly. We extract every distinct owner reference from source records and match by email address against Zoho User records. Owners with no matching Zoho User are held in a reconciliation queue; the customer's Zoho admin provisions the missing Users before record import resumes. Inactive Zoho Users can receive migrated records and be flagged for later activation.

Unim attachments are served via a separate Files API dimension, requiring one API call per file. We paginate attachment extraction to avoid 429 responses from the Unim API, extract the binary blob and metadata, and re-associate each file with the target record in Zoho CRM using the Attachments module. Original filenames and MIME types are preserved. Large attachment volumes (over 5,000 files) may extend the migration timeline and are scoped separately.

Unim tag associations are stored as linked records or array fields depending on the specific deployment. Tags are mapped to Zoho multi-select picklist fields on the target module, or to Zoho CRM Tags if the customer's workflow prefers a tag-based taxonomy. The customer chooses the tag strategy during scoping, as Zoho supports both approaches.

Webhook configurations in Unim are environment-level settings that reference Unim's internal API and cannot be meaningfully exported and re-imported into Zoho's webhook system. We document active webhooks (URL, trigger event, payload shape) in the migration handoff document. The customer's admin rebuilds these in Zoho using Webhooks, Deluge webhooks, or an integration middleware as appropriate.

Business-logic workflows built within Unim's application builder are tightly coupled to that deployment's custom object model. They do not translate across to Zoho's Blueprint and Deluge automation model. We export a written inventory of every active workflow with its trigger conditions, actions, and dependencies for the customer's admin to rebuild in Zoho Blueprint or Deluge.