Migration guide
Export Teamwork.com project lists, task list reports and the Time report as CSV, upload them to Pike templates, and connect your ledger. Budget five to six weeks.
Available now
Teamwork.com exports the project list, each task list report and the Time report as CSV or Excel, so you export one file per entity and upload each to the matching Pike template.
The Time report lists a task only when it is assigned to one user (not a team), has a start or due date, and has time on it. Check the report’s hour total against Projects → All time before you upload, and pull missing logs from the Teamwork.com API v3 time endpoints.
Available now
Teamwork.com exports invoices to QuickBooks Online, and to Xero as a file or through the older Xero Online connection, so your invoice history already exists in the ledger. Connect the same ledger to Pike.
Teamwork.com marks time logs as invoiced once they go on an invoice, and they can no longer be edited. Map those rows to `invoiced` `yes` so Pike does not bill them twice.
Entity map
Column one uses Teamwork.com’s labels. Pike matches people on the email of each Teamwork.com user and links records on project number and customer number.
Pike: Customers
Carries over: Company name, from the Company name column of the project list export.
You set in Pike: Customer number, currency and VAT ID. Check whether your export includes them.
Template columns: customerName, customerNumber, taxVatId, mainCurrency
Pike: Customer contacts
Carries over: The People export lists current users and contacts on your site. Check whether your file includes email and company for each contact.
You set in Pike: A customer number on each contact row.
Template columns: customerNumber, name, email, title, phone
Pike: Members
Carries over: Name. Check whether your Export to Excel file includes the email each user signs in with.
You set in Pike: Workspace role, team, position and cost profile.
Template columns: email, displayName, team
Pike: Projects
Carries over: Project name, company, category, owner, description, start and end date, project health, custom fields.
You set in Pike: A project number on every row. The project list export has no project code column.
Template columns: projectNumber, title, customerNumber, status, startDate, endDate, leadEmail
Pike: Project budget and billing type
Carries over: Budget type (Time & materials, Fixed fee, Retainer, Task list), amount as Time or Financial, start and end date.
You set in Pike: Budgets do not appear in the project list export. Copy them from Finance → Budgets on each project.
Template columns: projectNumber, billingType, budgetAmount, budgetHours
Pike: Phases
Carries over: Task list name and project.
You set in Pike: Start and end dates.
Template columns: projectNumber, phase
Pike: Tasks
Carries over: Title, task list, assignee, start and due date, from each task list report.
You set in Pike: A task status mapping. Check whether your report export includes completed tasks.
Template columns: title, projectNumber, phase, assigneeEmail, status, startDate, dueDate
Pike: Time entries
Carries over: Date, user, project, task list, task, hours. Check whether your export includes billable, invoiced and description columns.
You set in Pike: Map approved timesheets to `approved` and submitted ones to `submitted`.
Template columns: date, hours, email, projectNumber, taskTitle, note, billableStatus, approvalStatus, invoiced
Pike: Project hourly rate and cost profiles
Carries over: Billable rate per project. Cost rates go into member cost profiles.
You set in Pike: Cost profiles, entered by hand from site-wide user cost rates.
Template columns: hourlyRate
Pike: Invoice history from accounting
Carries over: Pike imports invoices from the QuickBooks or Xero ledger Teamwork.com exported them to.
You set in Pike: Nothing. The CSV route does not import invoices.
Teamwork.com picks a bill rate in this order: project rate, client role rate, role rate, then the user’s site-wide billable rate. Pike takes one `hourlyRate` per project, so use the project rate where one exists and the user rate otherwise.
A Time & materials budget counts Time in hours or Financial in money, which fill `budgetHours` or `budgetAmount`. Map Fixed fee budgets to `fixedFee`, Time & materials to `timeAndMaterials`, and rebuild Retainer budgets as Pike retainers.
Cost rates come only from each user’s site-wide cost rate, set by owner company site admins, and no project overrides them. Set one Pike cost profile per member from that rate.
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 CSV route copies a snapshot. A site admin runs every export the same day, since project admins see only their own projects’ time.
Done when: Every Teamwork.com export and the budget sheet 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 files. Nobody edits Teamwork.com after export day.
Done when: Every project row has a number, a customer number, a billing type and a budget.
Week 2
Workspace admin
Week 2 · Workspace admin
Admins set up Pike before the first upload, so they can give imported projects a team and a rate on day one.
Done when: Finance sees the ledger’s invoices in Pike. Every billable person has a cost profile.
Week 2 to 3
Workspace admin
Week 2 to 3 · Workspace admin
Customers, contacts, projects and phases, then members, tasks and time. Pike reports a row it cannot match with its line number.
Done when: Company, project, user and last-month hour counts match Teamwork.com.
Week 3 to 5
Delivery lead, finance
Week 3 to 5 · Delivery lead, finance
CSV has no ongoing sync, so the pilot team moves fully to Pike while everyone else logs time in Teamwork.com.
Done when: One invoice sent from Pike. Pilot time in Pike matches the same week in Teamwork.com’s Approvals tab.
Week 5 to 6
Migration owner
Week 5 to 6 · Migration owner
Close Teamwork.com on Friday evening. Everyone opens Pike on Monday.
Done when: Time admin shows every active member by Monday afternoon. Teamwork.com shows no time logs after Friday.
Week 6 to 9
Finance
Week 6 to 9 · Finance
Done when finance closes a month without opening Teamwork.com.
Done when: Month closed in Pike. Final Teamwork.com exports saved with two owners.
Rebuild
Questions
The Time report lists a task only when it is assigned to one user, has a start or due date, and has time logged. Compare the total with Projects → All time, and fill gaps from the API before you upload.
Budgets do not appear in the project list export, so copy each one from Finance → Budgets. Time & materials budgets fill `budgetHours` or `budgetAmount`, Fixed fee maps to `fixedFee`, and Retainer budgets become Pike retainers.
Teamwork.com applies a project rate first, then client role and role rates, then the user’s site-wide billable rate. Use the rate your clients pay on each project as its `hourlyRate`.
Not through CSV. Teamwork.com exports invoices to QuickBooks Online or Xero, so connect that ledger to Pike and Pike imports invoice history from it.
The site moves to Free Forever at the end of the billing cycle, with your data intact. The five most recently updated projects remain active, and Teamwork.com archives the rest as read-only. Deleting the site removes all data permanently.
ISO 27001
GDPR
SOC 2 Type IIBuilt to keep sensitive client data secure and private.
