Migrate from BQE CORE to monday Work Management

BQE CORE Projects map to monday.com Boards. The project name becomes the board title, project status maps to a Status column, and custom fields (project manager, client, budget) map to monday.com custom columns. CORE's phase and sub-phase hierarchy maps to monday.com Groups and Subgroups, though monday.com does not enforce a true hierarchical structure; we document the mapping so the customer understands the flattening. Multi-year project histories are preserved as date-filtered views within the board.

CORE Clients map to monday.com Groups on the project board, or to Person columns linking to monday.com contacts. Client name, phone, email, address, and billing contact transfer to monday.com Name, Email, and custom text columns. Address fields that exceed monday.com's standard address column format are stored in multi-line text columns. Clients with no active projects are created as standalone contact records in a separate Clients board for reference.

CORE Employee records map to monday.com team member profiles. Employee name, email, department, title, and cost/bill rates transfer to monday.com user profile fields and custom columns. CORE's security profile assignments (admin, manager, user) map to monday.com permission groups per board. Cost rates and bill rates, which are permission-gated in CORE's API, migrate as custom number columns if the API user has read-rate permission; otherwise we flag which employees have restricted rate access for manual post-migration entry.

CORE Time Entries map to monday.com items on a dedicated Time Tracking board. Each entry becomes an item with a Date column, Hours column (numeric), billable/non-billable flag, and a Link to Item connecting to the relevant Project board item. The employee-user link is preserved via the Assignee column. CORE's time entry notes migrate to monday.com item descriptions. If the customer is on monday.com Enterprise, we configure the native timesheet integration for ongoing time tracking post-migration.

CORE Expenses map to monday.com items on an Expenses board. Expense category, amount, date, project link, and reimbursement status transfer to monday.com columns. Receipt file references from CORE attach to monday.com items using the file column type. CORE's expense mark-up rates for client-billable expenses migrate as custom number columns. Non-reimbursable expenses are flagged in a Status column.

monday.com has no native invoice object, which is the most significant structural gap in this migration. CORE invoice records (invoice number, date, amount, status, line items) are preserved as custom columns on a dedicated Invoices board that links to the relevant Project board item. Invoice PDF attachments migrate as monday.com file attachments. The customer-admin must reconcile invoice financial summaries (AR balances, payment history, aging) against their accounting system post-migration, and we document the exact column mapping to facilitate that reconciliation.

CORE Vendors have no direct monday.com equivalent. We create a Vendors board with items representing each vendor, mapping vendor name, contact name, phone, email, payment terms, and AP account assignment to monday.com columns. Payment terms are stored as a text or select column. Vendors with outstanding AP balances in CORE are flagged in a Balance column for the customer's accounting team to reconcile.

CORE custom field definitions (label, type, length, list linkage) map to monday.com custom column types where available. Text fields map to Text Column, numeric fields to Number Column, date fields to Date Column, and yes/no fields to Checkbox Column. Select and multi-select custom lists in CORE map to monday.com Dropdown or Tags columns. Some CORE field types (currency, percentage, rate) have no exact monday.com equivalent and are stored in Number columns with the customer-admin noting the unit context.

CORE stores custom field values as separate linked records with entityId and entityType. We perform a two-pass extraction: first to collect all custom field values from the CustomFieldValue endpoint, then a join pass to stitch them to their parent Project, Employee, Invoice, or Expense records before writing to monday.com. This ensures complete records with all custom column values intact at the time of migration.

CORE project phases map to monday.com Groups within the Project board. Sub-phases map to monday.com Subgroups within each Group. CORE's phase-level billing amounts, budgeted hours, and percent complete migrate as custom columns on the Group. We note that monday.com does not support nested hierarchical views of subgroups within groups, so the phase hierarchy is flattened; customers with complex multi-level phase structures may need to use multiple boards or status labels to represent all levels.

For customers on monday.com Enterprise, CORE time entries can be mapped to monday.com's native timesheet integration, which allows employees to log time against project items. We configure the integration during the post-migration setup phase, mapping CORE project-phase-employee combinations to monday.com project-item-employee timesheet entries. Customers on lower monday.com plans use a custom Time Tracking board as the migration target.

CORE's Chart of Accounts (account numbers, types, balances, sub-account hierarchies) is an accounting concept with no monday.com equivalent. We extract the account structure and deliver it as a structured CSV inventory for the customer's accounting team to import into their chosen accounting tool (QuickBooks, Xero, Sage) post-migration. This is documented as a data deliverable, not a monday.com board object.

CORE fiscal year definitions (including any Migrated Fiscal Years created during onboarding from historical data) do not map to monday.com because monday.com has no native fiscal period accounting concept. We extract all fiscal year definitions and deliver them as a written calendar reference for the customer's reporting team to configure in monday.com's fiscal year settings and any connected BI tools. Multi-year financial data spanning fiscal year boundaries is preserved with its original dates and flagged for fiscal-based reporting.

CORE User records (email, name, security profile, screen-level permissions) map to monday.com team member profiles with board-level permission groups. CORE's permission-gated access to cost rates and bill rates is handled by extracting rates where the API user has Allow read rate permission and flagging restricted employees. monday.com's permission model is board-level rather than field-level, so any field-level visibility rules from CORE are noted as custom column permissions to configure post-migration.

CORE uses a project status workflow rather than a CRM-style pipeline. monday.com's board Status column can represent project stages (Active, On Hold, Complete, etc.), but CORE's billing-status and invoice-status workflow stages have no monday.com equivalent. We map CORE's project status values to monday.com Status column options and document the gap for the customer's project management team.