Migrate from BQE CORE to Microsoft Project

BQE CORE Projects map directly to Microsoft Project files or Project Online projects. CORE's project name, description, start date, and target end date migrate to MS Project's Name, Notes, Start, and Finish fields. Project status (Active, On Hold, Completed) does not have a direct MS Project equivalent; we set the project's schedule mode and percent complete based on CORE's status flags.

BQE CORE Phases attached to a Project map to MS Project Summary Tasks. The CORE Phase name becomes the summary task name; phase start and end dates map to the summary task Start and Finish. CORE's phase hierarchy (Phase under Project, Sub-phase under Phase) translates to a two-level outline in MS Project. If CORE contains more than three nesting levels, we flatten extra levels to keep the MS Project outline manageable.

CORE Tasks under a Phase or Sub-phase map to MS Project Tasks. Task name, planned hours, planned start, and planned finish migrate directly. CORE's task-level custom field values (stored as linked Custom Field Value entities) migrate to MS Project enterprise custom fields or task-level notes. We stitch custom field values in a two-pass extraction to ensure the parent task exists before the value is assigned.

CORE Time Entries linked to a Project and Phase map to MS Project task actuals. We aggregate time entries by task and write the sum as actual work (hours) on the task assignment. Billable versus non-billable flags from CORE do not map to a standard MS Project field; we write the billable flag to a task-level custom field if one exists, or flag it in the migration inventory for the customer to configure post-migration. Historical time entries spanning multiple fiscal years require chunked processing to stay within CORE's per-minute API rate limits.

CORE Employees map to MS Project Resources. First name and last name concatenate to the Resource Name; email maps to the resource's email or contact field. Cost rates migrate if the API user has the Allow read rate permission; if rates are permission-gated, we may encounter null values and we flag these records in the reconciliation report. Bill rates do not map to a standard MS Project field; they are written to a resource-level custom field or listed in the inventory for the customer's PMO to configure.

CORE's employee cost rates and bill rates by role or date range do not have a native MS Project equivalent. MS Project Resources have a single cost rate table per resource. We map the most recent or most commonly used cost rate from CORE to the MS Project resource rate, and write a separate rate matrix to the migration inventory for the customer to manually configure tiered rates in MS Project if needed.

BQE CORE Expenses linked to Projects do not map to Microsoft Project because MS Project has no expense tracking object. We extract expense records (vendor, amount, date, category, reimbursement status) and write them to a CSV inventory that the customer's admin imports into a separate expense management tool or a Microsoft Excel-linked Power BI report. Receipt file references are exported as file paths for manual reattachment.

CORE Invoices and line items have no Microsoft Project equivalent. MS Project does not include a billing or accounts receivable module. We extract invoice records (invoice number, date, client, status, total) and line items to a CSV inventory for the customer's admin to use when setting up a separate billing system or when migrating to a tool like Microsoft Dynamics 365 Business Central. Invoice PDFs are exported as file references.

CORE Vendors with AP account assignments do not map to Microsoft Project. We extract vendor records (name, contact, payment terms) to a CSV inventory for migration to a separate accounting platform such as Microsoft Dynamics 365 Business Central, QuickBooks, or a vendor management module in the customer's chosen ERP.

CORE's complete Chart of Accounts with account types, numbers, balances, and sub-account hierarchies has no Microsoft Project equivalent. We extract the account structure to a CSV inventory for the customer's accounting team to import into their chosen ERP or GL system. This data should not be discarded as it represents the firm's historical financial record.

CORE Custom Field definitions (label, type, length, optional custom list linkage) per module map to MS Project enterprise custom fields. We create the destination custom field in the MS Project Enterprise Global or in the project-level custom fields before importing data. Custom field values stored as separate linked entities in CORE are stitched back to their parent records in a two-pass extraction before writing to MS Project.