Migrate your Avaza data

Projects are Avaza's top-level container. They carry billing method, budget, cost rate, and billable rate settings inherited from the contact or timesheet category level. We migrate projects 1:1, preserving dates, status, team member assignments, and custom fields.

Sections are grouping containers inside a project used to organise Tasks. They have a display order and no independent metadata. We migrate them in sequence with their parent project.

Tasks sit inside Sections inside Projects. Each task carries assignees, due dates, priorities, and flat-rate amounts. We preserve the full task hierarchy and assignee mapping.

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 can diverge from source settings. We map the timesheet record including its frozen rate values and flag any entries where the rate was overridden post-creation.

Expenses are linked to a project and carry amount, currency, category, billable flag, and receipt attachments. We migrate expenses as-is and preserve the billable flag for downstream invoicing.

Invoices are financial records that can include free-form line items, timesheet blocks, expense blocks, and task fixed amounts. They reference customers and carry payment status. We import invoices as completed records and flag any that were partially paid at migration time.

Quotes are distinct from invoices and have approval statuses and client-view links. Avaza can convert a quote to a project but the quote itself is not a project sub-object. We reconstruct quote line items as project-level data.

Customers are contacts billable at the account level. External Contacts are broader and include project collaborators and client portal users. Both are migratable and carry billing and payment-term settings.

Avaza differentiates between Project Collaborators, Timesheet/Expense Users, Admin/Finance Users, Resource Schedulers, and Chat-access Team Members. Role-based limits vary by tier. We map the user identity and role assignments and flag any role counts that exceed destination plan limits.

Timesheet Categories define the type of work logged and carry default billable and cost rates that cascade into projects and timesheet entries. We migrate categories and preserve their rate configurations.

File attachments on tasks, expenses, and invoices are stored internally. We migrate file references and re-attach files where the export includes the blob or a reachable URL. Files without a reachable URL are noted in the migration report.

Custom fields are available on Projects and Tasks and appear in filtered report views. They are not surfaced in the standard export grid without applying the correct filter context. We map named custom fields explicitly during the discovery phase.

Avaza exposes 48 named reports across Project Management, Finance, Expenses, and Exports sections. Reports are role-filtered. We pull from the Exports section for raw unformatted data suitable for import elsewhere.

Team Chat is an internal messaging layer without a documented export endpoint. Chat history is not included in data exports and we cannot migrate it. We flag this gap upfront during scoping.