Migrate from Avaza to Trello

Avaza Projects map directly to Trello Boards. Project name, description, billing method (Time & Materials, Fixed Fee, Internal), budget, and active/archived status transfer. Avaza project-level cost rates and billable rates are exposed to Project Manager and Finance Manager roles only; we require admin credentials and verify rate visibility in a test export before migration. Archived projects map to archived Trello boards. Projects with over 500 tasks may warrant a second Board to avoid Trello performance degradation on large boards.

Avaza Sections are grouping containers inside a project used to organize Tasks. We map them to Trello Lists within the Board by default, preserving display order. For teams that used Sections as category tags (e.g., 'Design', 'Development', 'QA') rather than sequential phases, we offer a Label-based alternative mapping where each Section becomes a Label color group. The customer chooses during scoping. Sections have no independent metadata beyond name and order.

Avaza Tasks map to Trello Cards with full hierarchy preserved. Assignees transfer as Card members, due dates as the Card due date field, priorities as Labels (High=Red, Medium=Yellow, Low=Green by default), and flat-rate amounts as a custom field or card description note. Subtasks do not exist as independent Avaza objects; any subtask pattern used in Avaza migrates as a separate Card with a cross-board or checklist relationship the customer defines during scoping.

Avaza timesheet entries are linked to a project, section, task, user, and timesheet category, with Billable Rate and Cost Rate copied into each entry at the time of logging. Trello has no time-tracking, time-log, or timesheet object. We do not migrate timesheet data. The frozen rate values stored in historical Avaza timesheets are preserved as a written extract for the customer to use in their destination accounting tool.

Avaza expenses are linked to a project and carry amount, currency, category, billable flag, and receipt attachments. Trello has no expense tracking object. We do not migrate expenses. Billable expenses flagged in Avaza are preserved as a written extract for import into the customer's accounting platform (Xero, QuickBooks, or similar). Non-billable expense history is documented as a reconciliation report.

Avaza invoices are composite financial records built from free-form line items, uninvoiced timesheet blocks, uninvoiced expenses, and task fixed amounts. Each invoice can reference customers and carry payment status. Trello has no invoicing, billing, or financial record object. We do not migrate invoices. Invoice data is preserved as a written extract from the Avaza Invoice Detail report for reconstruction in the customer's accounting platform.

Avaza quotes are distinct from invoices with their own approval statuses and client-view links. Avaza can convert a quote to a project in one click. Trello has no quoting or estimate object. We do not migrate quotes. Quote line items and approval status are preserved as a written extract for reconstruction in the customer's CRM or accounting tool.

Avaza Customers and External Contacts map to Trello Board members on the corresponding Board. We use the contact's email address as the member identifier and send Trello workspace invitations. Clients who were External Contacts or project collaborators in Avaza become Workspace Guests or Board members in Trello. Contact billing and payment-term settings have no Trello equivalent and are preserved as a written contact profile extract.

Avaza differentiates between Project Collaborators, Timesheet/Expense Users, Admin/Finance Users, Resource Schedulers, and Chat-access Team Members with role-based limits varying by tier. We map active Avaza users to Trello workspace members by email. Users who were only assigned Chat or Resource Scheduling roles in Avaza (and had no project task assignments) are documented for the customer's admin to provision manually in Trello.

Avaza timesheet categories define work types and carry default billable and cost rates that cascade into projects and timesheet entries. Trello has no timesheet category object. If the customer used Avaza timesheet categories as work-type tags (e.g., 'Design', 'Development', 'Consulting'), we offer to map these as Label color groups in Trello for visual filtering across cards. This is a discretionary mapping determined during scoping.

Avaza custom fields on Projects and Tasks appear only in filtered report views and require the correct filter context to export. We map named custom fields to Trello Card Custom Fields (available on Standard and Business Class plans). Custom field types (text, number, date, dropdown) map to the closest Trello custom field type. Project-level custom fields become Board-level custom fields on the target Board.

Avaza 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 flagged for manual re-upload. Trello card attachments inherit the same 10MB per file and 250MB per Board limits on Standard plan.

Avaza Team Chat stores messages in an internal messaging layer with no documented API endpoint for message history export. Chat channels, direct messages, and file attachments shared in chat are not included in any data export. We explicitly scope chat out of the migration and disclose this gap in the Statement of Work. The customer should communicate this to their team before the migration date.