Migrate from Unanet CRM by Cosential to Zoho CRM

Unanet contacts map directly to Zoho Contacts. The primary company association resolves to Account_Name via the Company lookup field in Zoho. Any unmatched companies create placeholder Accounts in Zoho to preserve the relationship integrity. Contact roles that were assigned on pursuits in Unanet are migrated as Zoho Deal Contact Roles, preserving the association between contacts and their related deals in the Zoho CRM environment.

Unanet's Company entity is the Account equivalent in Zoho CRM. Company hierarchies with parent/child relationships map to Zoho's Parent Account lookup field. Multi-address companies are split into Zoho Address subform records, with separate entries per address type such as Billing Address and Shipping Address to maintain the full location data structure in Zoho.

Unanet Pursuits map to Zoho Deals but require a custom pursuit_stage__c pick-list field to preserve AEC-specific stage names (e.g., Go/No-Go, RFQ Received, Proposal Submitted). Each Unanet pursuit pipeline maps to a Zoho Pipeline with its own Stage values. Probability, forecast category, and stage-entry timestamps migrate as custom fields.

Unanet pipelines are translated to Zoho Pipelines (available on Professional+). Each pipeline stage in Unanet maps value-by-value to a Zoho Deal Stage pick-list entry. Stage probability percentages are applied per stage in Zoho. Stage order and stage-entry timestamps are preserved in custom datetime fields.

Unanet calls and emails map to Zoho Tasks with Type = Call or Email. Unanet meetings with start/end times map to Zoho Events. Unanet notes migrate as Zoho Notes. Original timestamps, owners, and parent-record lookups are preserved. Activity type flags (call direction, meeting outcome) map to Zoho custom fields.

Unanet file attachments on pursuits and contacts are downloaded and re-uploaded to Zoho's Attachments module linked to the corresponding record. Proposal PDFs are stored in Zoho's Documents (Zoho Docs) and linked via a custom URL field on the Deal. File size limits (Zoho caps at 50MB per file) are enforced per upload.

Unanet's proposal automation — template population, conditional section logic, and PDF generation — has no direct Zoho CRM equivalent. We export the full template definitions (field mappings, conditional rules, output format) as a JSON reference document for your Zoho admin to rebuild using Zoho Blueprint for stage logic and Zoho Writer for document templates.

Unanet Projects link pursuits to delivered work. Zoho CRM has no native Project object. We create a Zoho Custom Module named 'Project' with fields mirroring Unanet's project properties (Project Name, Status, Start Date, End Date, Associated Deal lookup). Project-to-contact associations are preserved via a junction lookup.

Unanet users are matched to Zoho users by email address. Unmatched owners are flagged before migration with a recommendation to create Zoho users or assign records to a fallback owner. User-active/inactive status is read from Unanet's user endpoint and set in Zoho.

Unanet custom properties are created as Zoho custom fields in the appropriate module before data loads. Field data types are mapped: text to text, number to number, date to date, pick-list to pick-list. Multi-select pick-lists in Unanet map to Zoho multi-select fields. API names follow Zoho's camelCase convention (e.g., AEC_Pursuit_Type).

Unanet's role labels on company-contact associations, such as Project Manager, Estimator, or Contract Administrator, map directly to Zoho's Account Contact Roles module. Custom role labels that don't match Zoho's standard role set are stored in a custom pick-list field (Contact_Project_Role__c) on the Contact record, ensuring role context is preserved in Zoho CRM.

Unanet qualification documents, RFQ files, and proposal attachments linked to pursuits are migrated as Deal Attachments in Zoho CRM. A custom URL field (Original_Pursuit_URL__c) stores a reference back to the original Unanet record for audit trail purposes during the transition window, allowing users to trace the document origin in Unanet if needed.