Migrate your BQE CORE data

Projects in CORE include phases, sub-phases, and task-level hierarchies. We extract the full project tree including phase assignments and custom fields. When migrating from ArchiOffice, note that CORE adds an Additional Services phase automatically.

Time entries link to Projects, Employees, and Phases. CORE supports billable/non-billable flags and custom field values per entry. We preserve the full entry record including the employee-user link and any phase assignments.

Expenses are tracked per project and can include receipt attachments exported as file references. We map expense categories and reimbursement status to the destination schema.

Employee records include cost rates, bill rates, and security profile assignments. Rates can be hidden per-user via the Allow read rate permission. We extract rate values when accessible or flag them for customer confirmation.

Invoices reference Projects, Clients, and line items from time/expense entries. CORE supports multiple invoice statuses (draft, sent, paid). We map invoice records and line items but custom invoice templates require reconfiguration at the destination.

Vendor records include contact details, payment terms, and AP account assignments. We extract vendor data and map to the destination's vendor or supplier object.

CORE's accounting module includes a complete Chart of Accounts with account types, numbers, and balances. We map account structures to the destination ERP schema including any sub-account hierarchies.

Custom fields are defined per module (Project, Employee, Invoice, etc.) with a label, type, length, and optional custom list linkage. We extract definitions and map them to equivalent custom properties at the destination, noting any type mismatches.

Custom field values are stored separately from the entity and linked via entityId and entityType. We stitch these back to their parent records during extraction so the destination receives complete records with custom values inline.

User records include email, name, security profile, and screen-level permissions. CORE's permission model controls access to cost rates, bill rates, and specific modules. We map active users and flag any inactive or archived accounts for customer decision.

CORE creates fiscal year records and may generate Migrated Fiscal Years during onboarding from historical data. We extract all fiscal year definitions and flag any data that spans across fiscal year boundaries for accounting continuity.

CORE uses a project status workflow rather than a CRM-style pipeline. If the destination requires CRM Pipelines, we do not migrate this concept as it does not map directly to CORE's data model.