Migrate from HighQ to Zoho CRM

HighQ Sites represent collaboration workspaces containing files, tasks, and iSheets. Zoho CRM has no Site equivalent, so we map the site structure to a Zoho custom module (Site_Reference__c) storing site name, description, and creation date. Files and tasks within each site link to this record via lookup fields.

HighQ user accounts with name, email, and role map directly to Zoho CRM Users. Owner resolution happens via email match — if a Zoho User exists with the same email as the HighQ member, their User ID becomes the OwnerId on migrated records. Unmatched members are flagged for Zoho admin review before migration commits.

HighQ Tasks (title, assignee, due date, status, description) map to Zoho Tasks with Status field value mapping (Open/In Progress/Completed translate to Zoho Not Started/In Progress/Completed). HighQ task sequences and dependencies do not have Zoho equivalents and are documented as manual-rebuild items.

HighQ iSheets are custom relational tables with typed columns. Each iSheet becomes a Zoho Custom Module with fields created per column. Column types map to Zoho field types: text to Single Line, numbers to Number or Currency, dates to Date fields, and attachment columns to Zoho File Upload fields. The custom module API name uses the iSheet name with spaces removed.

Individual rows within a HighQ iSheet become records in the corresponding Zoho Custom Module. All column values transfer as field values. If the iSheet references other iSheets via lookup columns, those relationships map to Zoho Lookup fields on the custom module.

HighQ files (documents, PDFs, spreadsheets) download from HighQ Drive and re-upload to Zoho Attachments linked to the parent record (Contact, Account, Deal, or Custom Module record). Files exceeding Zoho's 25MB limit are split or linked via Zoho's external file storage option. Version history is preserved in a custom field (File_Version__c) if multiple versions exist.

HighQ Workflows automate task reassignment, date updates, and conditional actions across Sites and iSheets. Zoho Blueprint handles deal-stage automation and Zoho Workflow Rules handle field updates — but the logic cannot be migrated directly. We export workflow definitions as a structured JSON document with rule conditions and actions so your Zoho admin can rebuild them in Blueprint.

HighQ email templates attached to workflows do not migrate directly to Zoho CRM. While Zoho CRM has its own Email Templates section, the template formats are incompatible and cannot be imported automatically. We export HighQ email template content as HTML files preserving original formatting and styling, which your team can then manually import into Zoho's Email Template editor after migration completes. This preserves the template body text and design while requiring manual reconfiguration in the target system.

HighQ site-level roles (Admin, Member, Viewer) map partially to Zoho CRM Roles and Data Access Rules. Site-level file permissions do not translate to Zoho's record-level sharing model. We document the permission structure for your Zoho admin to configure sharing rules post-migration.

HighQ comments on files and iSheet rows migrate to Zoho Notes attached to the corresponding record. The original comment text, author email, and creation timestamp are all preserved during migration. Threaded reply chains are flattened into a single Note body with author attribution prefixes (e.g., [John Smith]: ) for readability within Zoho's flat note structure. This conversion preserves content and timing while altering the conversational hierarchy.

HighQ reporting on Site activity, task completion rates, and iSheet data summaries have no native Zoho CRM equivalent for direct migration. The underlying data including Tasks and Custom Module records does migrate successfully, so Zoho Reports and Zoho Analytics can recreate comparable analytical views. We provide comprehensive documentation of HighQ report definitions including filters, groupings, and chart configurations as a reference guide during your Zoho report setup phase.

HighQ Checklists containing sub-items within tasks migrate as individual Zoho Tasks linked via a custom lookup field to the parent task. The parent checklist item becomes the primary task, with each checklist sub-item converted to a related subtask. HighQ's checklist completion percentage does not map directly to a native Zoho field, so we store this metric as a custom field (Checklist_Completion__c) on the parent task record for reference after migration.