Migration guide
Run the raw reports in Avaza’s Exports section, save them as CSV and upload them to Pike templates, with five to six weeks from first export to cutover.
Available now
Avaza groups its raw data exports under Reports → Exports: one report each for customers, contacts, projects, tasks, timesheet entries and expenses, with no totals or formatting. Only Administrators see this section.
Avaza’s help centre does not say whether the export reports include archived projects or archived users. Compare each file’s row count with the matching list in Avaza before you upload.
Available now
Avaza syncs invoices, payments and customers to QuickBooks Online, and invoices to Xero. Connect the same ledger to Pike, and Pike imports customers and invoice history from it.
Avaza’s QuickBooks sync skips retainer invoices, and its Xero sync copies only invoices created after the Integration Start Date. Check older and retainer invoices in the ledger before you rely on the Pike import for history.
Entity map
Column one uses Avaza’s report and screen names. Pike matches people on email and links records on project code and customer number.
Pike: Customers
Carries over: Customer name and the columns you add with Show Columns.
You set in Pike: A customer number on every customer, from your ledger where it is connected.
Template columns: customerName, customerNumber, taxVatId, mainCurrency
Pike: Customer contacts
Carries over: External contacts per customer. Check whether your export includes email and title.
You set in Pike: The customer number of each contact’s company.
Template columns: customerNumber, name, email, title, phone
Pike: Projects
Carries over: Project code (where project codes are on), name and customer. Check whether your export includes Billing Method, Budget Type and budget.
You set in Pike: A project number where your account has project codes turned off.
Template columns: projectNumber, title, customerNumber, status, billingType, budgetAmount, budgetHours, hourlyRate
Pike: Project team
Carries over: Which people work on which project.
You set in Pike: Project members in Pike. The Pike templates have no project member file.
Pike: Tasks
Carries over: Tasks per project. Check whether your export includes assignee, due date and status.
You set in Pike: A status mapping from your Avaza task statuses to Pike statuses.
Template columns: title, projectNumber, description, status, phase, assigneeEmail, startDate, dueDate
Pike: Members
Carries over: Name and email. Avaza stores Billable Rate and Cost Rate on each person’s Person Details.
You set in Pike: Check whether the Contacts export lists team members. Workspace role, team and a cost profile from the cost rate.
Template columns: email, displayName, team, position
Pike: Time entries
Carries over: Timesheet rows per person and project. Avaza statuses are Draft, Pending, Approved, Automatically Approved, Rejected and Invoiced. Check whether your export includes status and the billable flag.
You set in Pike: Whether rejected time imports at all.
Template columns: date, hours, email, projectNumber, taskTitle, note, billableStatus, approvalStatus, invoiced
Pike: Expenses
Carries over: Expense rows per project. Check whether your export includes category and the billable flag.
You set in Pike: Expense categories that match the Expense Category Export.
Template columns: date, amount, projectNumber, email, category, description, billableStatus
Pike: Deals
Carries over: Open estimates per customer.
You set in Pike: Check whether your estimate export includes status and total, and fill `value` and `status` where it does not.
Template columns: title, customerNumber, status, value
Pike: Invoice history from accounting
Carries over: Avaza invoices and other transactions. Pike imports invoices from QuickBooks Online or Xero.
You set in Pike: Nothing. The CSV route does not import invoices.
Avaza sets the bill rate through each project’s Billing Method: Person Hourly Rate, Category Hourly Rate, Project Hourly Rate, Do not apply hourly rate, or Not Billable. Enter the rate the project bills at as `hourlyRate`, and set task rates in Pike where a project billed by timesheet category.
Map Budget Type to Pike: Total Project Fees to `budgetAmount`, Total Project Hours to `budgetHours`, and sum Person Hours or Category Hours budgets into `budgetHours`. Projects on Not Billable with fixed amounts per task import as `fixedFee`, with the fixed total as `budgetAmount`.
Avaza stores a Billable Rate and a Cost Rate on each person’s Person Details, and a cost amount on timesheet categories. Set each member’s Pike cost profile from the Avaza cost rate before the pilot.
The plan
The same steps as the main migration guide, with this tool's screens and settings.
Week 1
Migration owner, finance
Week 1 · Migration owner, finance
The first export is your migration data. Write down its date, because you run Timesheet Entries again for the days after it at cutover.
Done when: Raw Avaza exports in one dated folder, and a cutover Friday on the calendar.
Week 1 to 2
Operations lead
Week 1 to 2 · Operations lead
Clean the CSV copies. Nobody edits Avaza after export day.
Done when: Every project row has a project number, customer number, billing type and budget. Every person has the email they will sign in with.
Week 2
Workspace admin
Week 2 · Workspace admin
Connect the ledger first, so the customer numbers in your Avaza files match the customers Pike imports from QuickBooks or Xero.
Done when: Finance sees the ledger’s customers and invoices in Pike. Every billable person has a cost profile.
Week 2 to 3
Workspace admin
Week 2 to 3 · Workspace admin
Customers and contacts, then projects, then members, then tasks, time entries and expenses. Pike reports a row it cannot match with its line number.
Done when: Customer, project, person and last-month hour counts match Avaza.
Week 3 to 5
Delivery lead, finance
Week 3 to 5 · Delivery lead, finance
On CSV there is no ongoing sync. The pilot team logs time in Pike only, and everyone else submits Avaza timesheets until cutover.
Done when: One invoice sent from Pike. No pilot team time in Avaza after the pilot start date.
Week 5 to 6
Migration owner
Week 5 to 6 · Migration owner
Close Avaza on Friday evening and upload the time logged since your first export.
Done when: Time admin shows every active member by Monday afternoon. Avaza shows no time after Friday.
Week 6 to 9
Finance
Week 6 to 9 · Finance
Done when finance closes a month without opening Avaza.
Done when: Month closed in Pike. Final Avaza exports saved with two owners. Avaza on the Free plan or closed.
Rebuild
Questions
The Avaza report viewer offers PDF, Excel, Word and other formats, but no CSV. Export to Microsoft Excel (.xlsx) and save the file as CSV UTF-8 before you upload.
Avaza limits reports outside the Exports section to 11 columns. Use the raw export reports, and set Show Columns and Sort Columns before you click Preview.
Approved and Automatically Approved map to `approved`, Pending to `submitted`, and Draft to `draft`. Invoiced entries import as `approved` with `invoiced` = `yes`. Decide with finance whether Rejected time imports at all.
Not through CSV. Connect QuickBooks Online or Xero, which Avaza syncs invoices to, and Pike imports invoice history from the ledger. Check retainer invoices and invoices from before your Xero Integration Start Date separately.
Cancelling moves the account to the Free plan, where the data remains and you can still sign in and export. The account must fit the Free plan’s limits first, so archive extra users and projects before you switch.
ISO 27001
GDPR
SOC 2 Type IIBuilt to keep sensitive client data secure and private.
