Migrate from BQE CORE to Asana

BQE CORE Projects map directly to Asana Projects. The project name, description, status, start date, and due date map to Asana name, notes, and date fields. Project-level custom fields migrate to Asana custom fields on the Project. We preserve the project hierarchy for clients with multiple related projects by creating an Asana Portfolio grouping. BQE CORE's project-level budget fields have no direct Asana equivalent and require either a custom field or a note for the customer to track post-migration.

BQE CORE Phases map to Asana Sections within a Project. Sub-phases map to sub-Sections or as a top-level task with the sub-phase name as a section header task. Phase hierarchy depth of up to four levels in BQE CORE flattens to two levels in Asana (Project > Sections), so we reparent sub-phases to the nearest Section and document the hierarchy collapse for the customer's admin. Phase-level custom fields migrate as Section-level custom fields where supported.

BQE CORE Tasks (within Phases) map to Asana Tasks within the corresponding Section. Task name, description, start date, due date, assignee (mapped to an Asana member), and priority map to their Asana equivalents. Task status in BQE CORE maps to the Asana completion state (completed vs. open). Task-level custom fields migrate as custom fields on the Asana Task.

BQE CORE Time Entries map to Asana Tasks using a two-pass approach: first we extract all time entries, then we create a placeholder Task for each distinct date-employee-project-phase combination and populate custom fields for hours_worked, billable_hours, non_billable_hours, and time_entry_date. This preserves the billable time data without creating duplicate tasks where multiple time entries exist for the same work item. The original time entry notes migrate to the task description.

BQE CORE Employee records map to Asana Workspace members. We extract name, email, role, and the employee photo where available, and invite each active employee to the Asana Workspace. Cost rates and bill rates are permission-gated in BQE CORE via the Allow read rate permission; if the migration API user lacks rate visibility, these fields may return null or zero. We request elevated API credentials with rate visibility before extraction or flag restricted employees to the customer.

BQE CORE Clients map to Asana as Project collaborators with viewer or commenter access, or as a dedicated Asana Team that owns client-facing projects. Client contact records (name, email, phone, address) migrate to the project collaborator profile. If the destination uses a CRM integration alongside Asana, client records can alternatively be held in the CRM and referenced in Asana via a custom field lookup.

BQE CORE Expenses have no direct Asana equivalent. Expenses track reimbursable and non-reimbursable costs linked to Projects and Employees with receipt attachments. We do not migrate Expenses as a native object; instead, we export a structured CSV of expense records (vendor, amount, category, date, project, employee, reimbursement status) that the customer can import into their chosen accounting tool or a dedicated expense management platform.

BQE CORE Invoices have no Asana equivalent. Invoices reference Projects, Clients, and line items from time and expense entries with statuses (draft, sent, paid). We do not migrate Invoices. We recommend the customer exports invoice history as a PDF archive from BQE CORE and manages future invoicing in a dedicated accounting tool (QuickBooks, Xero, or FreshBooks) integrated with Asana for project and time data.

BQE CORE's Chart of Accounts with account types, numbers, balances, and sub-account hierarchies has no Asana equivalent. We do not migrate this object. For firms that rely on CORE's accounting module, we recommend either retaining CORE for accounting only while migrating project and task work to Asana, or exporting the chart of accounts to the destination accounting tool as part of a broader ERP migration.

BQE CORE Vendors with contact details, payment terms, and AP account assignments have no Asana equivalent. We do not migrate Vendors. A vendor contact list export as a CSV or into a dedicated accounting tool covers the data without requiring a rebuild in Asana.

BQE CORE custom fields (defined per module: Project, Task, Employee, Invoice, etc.) with type, label, and length map to Asana custom fields. Data types map as follows: Plain Text to Asana text, Numeric to Asana number, Currency to Asana number with a note, Decimal to Asana number, Date to Asana date, and Custom Lists to Asana enum. Custom fields without an exact Asana type map to text.

BQE CORE stores custom field values as separate linked entities rather than on the entity itself. We perform a two-pass extraction: first to collect all custom field values linked by entityId and entityType, then a join pass to stitch them back to their parent records. This ensures complete records in Asana with every custom field populated. The two-pass approach adds a processing step but is required for data integrity.

BQE CORE user records (email, name, security profile, screen-level permissions) map to Asana Workspace members. CORE permission profiles controlling access to cost rates, bill rates, and specific modules do not map to Asana's member-guest model. We map active CORE users to Asana members and flag inactive users for the customer admin to decide on Asana guest licensing. BQE CORE's module-level access restrictions have no Asana equivalent.