Migrate from HighQ to monday CRM

HighQ Sites map to Monday Workspaces as the top-level organizational container. Site-level permissions translate to Monday permission groups. If the HighQ deployment uses multiple sites for different business units, each becomes a separate Monday Workspace — workspace-level isolation must be configured before data lands.

iSheets are spreadsheet-like tables — we infer the CRM entity type from column signatures. An iSheet with 'First Name', 'Last Name', 'Email' columns maps to a Monday CRM People board. An iSheet with 'Deal Name', 'Amount', 'Stage' columns maps to a Monday CRM Deals board. All other iSheets map to custom Boards with column-type mapping (text → Text, number → Numbers, date → Date, user-picker → Person).

Each iSheet row becomes a Monday Item on the target board. The item name defaults to the iSheet's designated name column. Sub-rows within an iSheet (if used) map to Monday Subitems on the target board. All column values transfer as corresponding Monday column types.

HighQ user-picker columns hold user references. These map to Monday Person columns, which link to Monday CRM People. Owner resolution happens by email match against Monday workspace members. Unresolved owners flag before migration so your team can invite or reassign before data commits.

HighQ formula columns compute values client-side from other column inputs. Monday Formula columns exist but rely on different function syntax. During migration, formula results migrate as static text values — the computed value at snapshot time — preserving the data in Monday even though the formula itself does not transfer. To restore dynamic recalculation in Monday, a Monday automation specialist must recreate each formula using Monday's Formula column syntax and reference the correct column IDs. We flag all formula columns in the pre-migration audit so this manual recreation step is not overlooked.

HighQ Drive files attached to iSheet rows re-upload to Monday Files attached to the corresponding Items. Monday enforces a 250MB per-file upload limit — files exceeding this are flagged for chunked upload or manual download-link archival. File metadata (name, size, upload date, uploader) preserves during migration.

HighQ tasks within an iSheet context map to Monday Subitems on the parent Item. Standalone HighQ tasks (not linked to a sheet) map to Items on a dedicated Tasks board. Status, due date, priority, and assignee columns translate to Monday Status, Date, Numbers (priority), and Person columns respectively.

HighQ Workflow rules (triggers, conditions, actions) do not transfer to Monday Automations — the rule engines use incompatible schemas. We export the rule definitions as a structured JSON document that Monday automation specialists can use as a rebuild blueprint. Sandbox-to-production workflow differences require explicit documentation since HighQ sandbox rules must be manually rebuilt in production.

HighQ user accounts (email, display name, site role) map to Monday workspace members. Site-level HighQ roles (Admin, Member, Guest) map to Monday permission groups. Users who exist in HighQ but not in Monday are flagged with a 'no-match' status — your team can invite them to Monday before the migration owner-resolve step.

HighQ Sandbox environments are development/staging spaces that must not be migrated as live data. We extract the sandbox configuration as a reference document for the Monday implementation. Any workflow rules built in Sandbox require manual rebuild in Monday's production workspace.

HighQ documents stored in Files or attached to iSheet rows migrate to Monday Files. For documents over 250MB, we create a Monday Link column entry pointing to the source file URL for reference. Document version history is preserved as a text field on the item since Monday Files do not maintain per-version history natively.