Projects
Pike: Projects
Carries over: Name and the tasks you map into it.
You set in Pike: Customer, project number, billing type, budget, hourly rate and team. Asana projects store none of these.
Template columns: projectNumber, title
Migration guide
Move from Asana to Pike
Connect Asana, map each Asana project to a Pike project, and run Import once when the last team moves. Budget five weeks from connection to cutover, then one month-end in Pike.
Available now
Pike reads Asana through the Asana API. Tasks, subtasks, sections and comments import into the Pike projects you map them to.
- In Pike, go to Workspace settings → Integrations → Asana, click Add integration, and authorize Pike for your Asana workspace in the popup.
- On the integration page, map each Asana project to a Pike project. Create the Pike projects first, with their customer, billing type and budget, because Asana stores none of these.
- While teams move one at a time, click Import data and leave Read on for tasks. Changes in Asana reach Pike in real time through Asana webhooks.
- When the last team moves, choose Import once. It copies projects, sections, tasks, subtasks and comments as text, then disconnects.
Pike never writes to Asana, during the import or after it. A task removed in Asana shows as Removed in Asana in Pike, with its history intact.
Available now
Use CSV when nobody can authorize Pike in your Asana workspace, or when you bring over a few projects and their tracked time.
- Open each project, click the drop-down arrow next to the project name and choose Export → CSV. Asana exports one file per project.
- Map Name, Assignee, Due Date, Notes and Parent Task to the Tasks template. Asana writes subtasks as their own rows with the parent named in Parent Task.
- If your plan includes time tracking, export time entries by person and date. Asana writes 1h 30min as 1:30, so convert each duration to decimal hours for `hours`.
- Upload projects, members, tasks, then time entries under Workspace settings → Integrations → CSV, using the Pike template columns.
Asana’s help centre lists the time entry export as limited availability. Check whether your workspace shows it before you plan the CSV route around Asana time.
Entity map
What each Asana record becomes in Pike
Column one uses Asana’s own labels. Asana has no client, rate or invoice records, so your team creates customers and sets billing in Pike. Pike matches assignees on the email of each Asana user.
Sections
Pike: Task status
Carries over: Section name, through a status mapping you edit on the integration page.
You set in Pike: The status each section maps to.
Tasks and subtasks
Pike: Tasks and subtasks
Carries over: Task name, notes as description, assignee, due date, tags as labels, completed state, attachments as links.
You set in Pike: Billable status. Asana custom fields do not import, so recreate the ones you report on as Pike task properties.
Template columns: title, projectNumber, description, assigneeEmail, dueDate
Comments
Pike: Task comments
Carries over: Comment text, through Import once.
You set in Pike: Nothing.
Members
Pike: Members
Carries over: Email, matched to the Pike member who signs in with it.
You set in Pike: Workspace role, team, position and cost profile.
Template columns: email, displayName
Estimated time and Actual time
Pike: Time entries
Carries over: Time entries by person and date, through the Asana time export where your plan has it.
You set in Pike: Billable status and approval for each entry.
Template columns: date, hours, email, projectNumber, taskTitle
Asana stores no bill rates, cost rates or money budgets. Set billing type, budget and hourly rate on each Pike project before the pilot team logs time, or Pike shows zero revenue on that work.
Asana time tracking adds Estimated time and Actual time fields to a project. Import once does not copy them, so bring tracked time through the CSV time export or start time fresh in Pike.
Give every member a cost profile in Pike. Asana records no cost per person, and Pike calculates margin from the cost profile.
The plan
Seven steps out of Asana
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
Freeze scope and export
Pike reads Asana directly. The export in week one is your archive copy of every project you close.
- Pick a cutover Friday and list the Asana projects that move, with the client each one bills.
- Export each project from Export → CSV and save the files in one folder.
- If you track time in Asana, export time entries by person and date for every month you still invoice.
Done when: Archive exports in one folder, a cutover Friday on the calendar, and every Asana project matched to a client.
Week 1 to 2
Operations lead
Week 1 to 2 · Operations lead
Clean the data in Asana
Pike imports what Asana stores, so tidy sections and assignees in Asana before you connect.
- Use the same section names across projects that share a workflow. Each section maps to one Pike task status.
- Assign open tasks to people with the email they will sign in to Pike with.
- Move any figure you report on out of Asana custom fields and into notes or tags. Custom fields do not import.
Done when: Sections match across projects. Every open task has an assignee with a Pike email.
Week 2
Workspace admin
Week 2 · Workspace admin
Build the workspace shell
Asana has no clients or rates, so admins set up every commercial detail in Pike before the first import.
- Connect your accounting system and run its Import data, so customers come from the ledger.
- Create one Pike project per Asana project, with customer, billing type, budget and hourly rate.
- Set a cost profile for everyone who logs billable time.
Done when: Every Asana project has a Pike project with a customer, billing type and budget.
Week 2 to 3
Workspace admin
Week 2 to 3 · Workspace admin
Connect and import
Map each Asana project to its Pike project, then import tasks in dependency order, tasks before subtasks.
- Add the Asana integration and map every project on the integration page.
- Edit the status mapping so each section maps to the right Pike status, then click Import data.
- Retry anything listed under Sync issues and compare task counts on three projects with Asana.
Done when: Task and subtask counts on every mapped project match Asana.
Week 3 to 4
Delivery lead, finance
Week 3 to 4 · Delivery lead, finance
One team in Pike, the rest in Asana
Move one team with a live client project and an invoice due. Asana changes reach Pike in real time while the others finish the sprint.
- The pilot team plans tasks and logs time in Pike only. Everyone else plans in Asana.
- Finance approves the pilot team’s time in Time admin and sends one invoice from Pike.
- Compare the pilot project’s hours and budget burn with what the delivery lead expected. A gap means a missing rate or cost profile in Pike.
Done when: One invoice sent from Pike. The pilot team made no Asana edits during the sprint.
Week 4 to 5
Migration owner
Week 4 to 5 · Migration owner
Cutover weekend
Close Asana on Friday evening with Import once, then make the old projects comment-only.
- Friday: run Import once so comments copy as text, and check the last week’s tasks in Pike.
- A project admin sets each moved project’s members to Commenter or Viewer, or archives the project. Only project admins can archive an Asana project.
- Monday: everyone plans and logs time in Pike. Pin one message with links to log time, find tasks and ask for help.
Done when: Time admin shows every active member by Monday afternoon. No Asana task changed after Friday.
Week 5 to 8
Finance
Week 5 to 8 · Finance
First month-end in Pike
Done when finance closes a month without opening Asana.
- Approve all time, invoice every billable project from Pike and send the invoices to accounting.
- Deprovision people who no longer need Asana from the organization, then check the seat count in Asana billing.
- On Enterprise+, request the JSON organization export as a final archive. On other plans, the project CSVs from week one are your archive.
Done when: Month closed in Pike. Asana exports saved with two owners. Asana seat count lowered.
Rebuild
Set these up in Pike by hand
- Clients and billingSet customer, billing type, budget and rate on each project.Pike docs
- Asana custom fieldsRecreate the fields you report on as task properties.Pike docs
- Project templatesRebuild your Asana templates as Pike project templates.Pike docs
- Workload and capacityPlan each person’s hours per project as allocations.Pike docs
Questions
Moving from Asana: common questions
Does Pike import our Asana time tracking?
Not through Import once, which copies projects, sections, tasks, subtasks and comments. Asana’s time export lists entries by person and date, so upload those rows to the Pike time entry template.
What happens to Asana custom fields?
They do not import. Recreate the ones you report on as Pike task properties before the import, and copy any value you need into notes or tags in Asana first.
Can we keep planning in Asana and use Pike for time and margin?
Yes. Leave the integration connected with Read on, and Asana tasks sync into Pike in real time through Asana webhooks. Pike tracks time, budgets and margin on the same tasks and never writes back to Asana.
How do we stop people editing Asana after cutover?
A project admin changes each member’s access to Commenter or Viewer, or archives the project. Only project admins can archive in Asana, so name one per project before cutover.
Do Asana attachments come across?
Attachments import as links to the file in Asana. Download any file you need after Asana closes and attach it to the Pike task.
Your business runs better on Pike.
ISO 27001
GDPR
SOC 2 Type II
Built to keep sensitive client data secure and private.