Migrate from Avaza to monday Work Management

Avaza Projects map 1:1 to monday.com Boards. Each Avaza project carries billing method, budget, cost rate, and billable rate settings inherited from the contact or timesheet category level. We translate these into monday.com Board columns: billing method becomes a Status or Dropdown column, budget becomes a Numbers column, and cost/billable rates become Numbers columns or a linked Rate Board. The project name becomes the Board name, and the project description becomes the Board description or a Workdoc. Project status (active, archived) maps to Board folder or archive state in monday.com.

Avaza Sections are grouping containers inside a Project used to organise Tasks. They have a display order and no independent metadata. We map Sections to monday.com Groups within the target Board, preserving the display order and renaming them to match the source Section name. Groups provide the first level of hierarchy inside a Board, replicating the Project → Section relationship as Board → Group.

Avaza Tasks sit inside Sections inside Projects. Each task carries assignees, due dates, priorities, flat-rate amounts, and task-level custom fields. We map Tasks to monday.com Items within the corresponding Group. Assignee maps to the People column, Due Date to the Date column, Priority to a Labels or Status column, and flat-rate amounts to a Numbers column. Sub-task relationships in Avaza (if used) map to monday.com Sub-items attached to the parent Item.

Avaza Timesheets are time entries linked to a project, section, task, user, and timesheet category. Billable rates and cost rates are copied into each timesheet record from the project at entry time and retained as frozen historical values. We preserve these frozen rate values by creating a Time Tracking board or adding a Time Tracking column to each project Board, storing the date, duration, user, category, and the preserved billable and cost rates as custom Numbers columns. We do not recompute from the current project rate because Avaza's historical rate snapshot must remain intact for billing accuracy.

Avaza Expenses are linked to a project and carry amount, currency, category, billable flag, and receipt attachments. We create a dedicated Expense Board in monday.com and map each expense to an Item, with amount as a Numbers column, currency as a Labels or Dropdown column, category as a Labels column, and the billable flag as a Toggle column. Receipt attachments migrate as file attachments on the Item. The billable flag is preserved so that downstream invoice reconstruction can filter uninvoiced versus invoiced expenses.

Avaza Invoices are composite financial records built from free-form line items, uninvoiced timesheets, uninvoiced expenses, and task fixed amounts, each grouped by project, category, user, section, or task. monday.com has no native invoice object. We create a Finance Board and map each Avaza invoice to an Item, with invoice number, date, customer reference, total amount, currency, and payment status as columns. Line item detail is stored as sub-items on the Item, pulling from the migrated timesheet and expense data already resident in monday.com. The customer reconciles the Finance Board against their accounting system post-migration.

Avaza Quotes have approval statuses and client-view links distinct from Projects and Invoices. monday.com has no native quote object. We create a Sales Board and map each Quote to an Item, with quote number, date, customer, total amount, status (Draft, Sent, Approved, Declined), and expiry date as columns. Line item detail is stored as sub-items on the Quote Item. The client-view link does not migrate and must be recreated in monday.com or via a document generation integration.

Avaza Customers are contacts billable at the account level; External Contacts include project collaborators and client portal users. Both carry billing and payment-term settings. We map these to a Contact Board in monday.com (Name, Email, Phone, Company, Payment Terms as columns) and link them to Items in project Boards via the People column or as an Item in a Contacts Board with cross-board linking. User contact records are cross-referenced against the Users mapping to avoid duplication.

Avaza differentiates between Project Collaborators, Timesheet/Expense Users, Admin/Finance Users, Resource Schedulers, and Chat-access Team Members. We map all active Avaza users with a seat assignment to monday.com Workspace Members, using email as the match key. We flag any Avaza user referenced on timesheet or expense records who does not have a monday.com seat for admin provisioning before migration. Role differences (Admin vs Member) map to monday.com Workspace permission levels.

Avaza Timesheet Categories define the type of work logged (e.g., Development, Design, Consulting) and carry default billable and cost rates that cascade into projects and timesheet entries. We map Categories to monday.com Labels on the Time Tracking Board or as a Labels column on the relevant project Boards. The default billable and cost rates stored at the category level are preserved in the migrated timesheet records as frozen values rather than recomputed, since Avaza copies these rates into each timesheet at entry time.

File attachments on Avaza tasks, expenses, and invoices are stored internally. We migrate file references where the export includes a reachable URL or blob, attaching them to the corresponding monday.com Item using monday.com's file upload API. Files without a reachable URL are flagged in the Statement of Work as a gap for manual re-upload by the customer. Avaza's Team Chat file attachments are excluded because Team Chat itself is not migratable (no export endpoint).

Avaza Custom Fields on Projects and Tasks appear in filtered report views and require explicit filter context to surface in exports. We perform a field-by-field review during scoping to identify all named custom fields, their types (text, number, date, dropdown, checkbox), and their parent object (Project or Task). We create equivalent monday.com Columns on the target Board or Items, matching the field type to the closest monday.com column type (text to Text, number to Numbers, date to Date, dropdown to Dropdown or Labels, checkbox to Toggle). Custom fields without a clear monday.com equivalent are stored as text Notes columns with the field name as the column header.

Avaza exposes 48 named reports across Project Management, Finance, Expenses, and Exports sections, all role-filtered. We do not migrate reports as executable objects because monday.com's reporting model (widgets on Dashboards) is structurally different. Instead, we extract the named report definitions from Avaza's Exports section as structured data, map each report's metrics and filters to monday.com Dashboard widgets, and document the mapping as a rebuild guide for the customer's admin. The dashboard rebuild itself is out of migration scope.