Migrate your HighQ data

Sites are the top-level organizational container in HighQ. All content (Files, iSheets, Workflows, Portals) lives within a Site. We map Site hierarchy and preserve the site-tree structure in the destination, though destination-native equivalents (e.g., SharePoint sites) must be manually mapped.

The Files module stores document binaries with version history. We export files with their metadata (upload date, uploader, version stack) from HighQ Drive. The file binary and version chain are preserved intact during migration.

iSheets are customizable tabular datasets with column-level type definitions (text, number, date, user reference, etc.). The API uses a sequence parameter to map column order. We extract the full iSheet schema (column names, types, sequences) alongside all row data and reconstruct it in the destination with equivalent column types.

Workflows define automated task sequences and rules within a Site. A known HighQ limitation is that workflows built in sandbox must be manually rebuilt in production—no automated migration between environments. We document all workflow definitions and rule chains as advisory artifacts for manual reconstruction in the destination.

Tasks are standalone or workflow-attached action items with assignees, due dates, and statuses. We extract tasks and their metadata. Where the destination has a task object, we map assignee and status fields; standalone tasks without a destination equivalent are imported as generic records.

Client Portals provide external-facing collaboration spaces scoped to a Site. Permissions and portal membership lists are exported and mapped to the destination's closest equivalent (e.g., Microsoft Teams guest access, SharePoint site membership). Portal structure and content are preserved as file-and-iSheet bundles.

User accounts with role-based permissions are scoped per Site. We export user identities, display names, and role assignments. External collaborators and client portal users are tracked separately from internal users and must be mapped to corresponding identity records in the destination.

HighQ uses a role-based permission model at the Site and module level. Role definitions (Admin, Member, Guest, and custom roles) and per-object access grants are exported. Mapping to destination roles requires manual alignment of capability sets.

Custom fields are primarily implemented within iSheets. Column-level custom field definitions and their data values are migrated together as part of the iSheet export. We preserve custom field IDs and display names for traceability.

Activity feed entries and notification history are ephemeral system events. HighQ does not expose a dedicated activity log export endpoint, and the data is not meaningful for migration to a new platform. We do not attempt to migrate activity history.

Document version history is preserved in the Files module. We export all versions of each document binary along with version timestamps and author attribution. The destination receives the complete version chain for each file.