Spaces or folders per client
Pike: Customers
Carries over: Space or folder name, where your team set one up per client.
You set in Pike: Customer number, VAT ID and currency.
Template columns: customerName, customerNumber
Migration guide
Move from Wrike to Pike
Export Wrike projects, the Timelog view and the user list, save them as CSV for the Pike templates, and plan five to six weeks from first export to cutover.
Available now
Wrike exports projects and tasks to Excel from each space, and time from the Timelog view. You export each on the day you freeze changes and save the files as CSV UTF-8.
- Open each space, click the three-dot menu in the top bar and choose Export → Excel → Projects, folders and all tasks. Collaborators, Contributors and Viewers cannot export.
- For Created Date, Completed Date and ID, add those columns to a Table View and use Export this table to Excel. Export Project to Excel leaves them out.
- Switch each space to Timelog view, clear filters, click Export and choose Excel. Export the user list from Settings → Account Management → Users: the three-dot menu next to All users → Export users to Excel → CSV.
- Upload customers, projects, phases, members, tasks, then time entries under Workspace settings → Integrations → CSV, using the Wrike column mapping.
An Excel export stops at 65,000 rows and 256 columns. Split large spaces by project or folder. On Pinnacle and Apex, BI Export also writes Projects, Tasks, Users and Timelog entries as CSV files.
Available now
Wrike exports the Timelog view as a QuickBooks file and connects to HubSpot and Salesforce. Connect the same systems to Pike, so finance and sales use the same ledger and CRM through the move.
- Connect QuickBooks, or the ledger your team invoices from, under Workspace settings → Integrations and run Import data for customers and invoice history.
- If HubSpot deals create Wrike projects from blueprints, connect HubSpot to Pike and turn off the Wrike Integrate recipe at cutover.
- If your team uses Wrike for Salesforce, connect Salesforce to Pike for accounts and opportunities, and stop creating Wrike projects from Salesforce records at cutover.
Wrike records no invoices. Pike imports invoice history from the ledger and has no CSV template for invoices.
Entity map
What each Wrike record becomes in Pike
Column one uses Wrike’s labels. Wrike has no client record, so decide whether a space or a folder represents each client before you clean the files.
Projects
Pike: Projects
Carries over: Title, status, start and finish dates, project owner.
You set in Pike: Project number and billing type.
Template columns: projectNumber, title, customerNumber, status, startDate, endDate, leadEmail
Budget (financial field)
Pike: Project budget
Carries over: A money budget entered by hand on the project, on plans with budgeting.
You set in Pike: An hours budget, if you track one outside Wrike.
Template columns: budgetAmount, budgetHours
Subfolders and subprojects
Pike: Phases
Carries over: Name and parent project.
You set in Pike: Start and end dates.
Template columns: projectNumber, phase
Tasks and subtasks
Pike: Tasks
Carries over: Title, status, assignees, start and due dates, duration, effort, billable flag.
You set in Pike: One assignee per row, and one row per task. A task tagged in several projects appears once per location in the export.
Template columns: title, projectNumber, phase, status, assigneeEmail, startDate, dueDate, billableStatus
Users and job roles
Pike: Members
Carries over: User list export (check its Show Settings panel for email), and job role.
You set in Pike: Team, workspace role and cost profile.
Template columns: email, displayName, position
Timelog entries
Pike: Time entries
Carries over: Tracked date, hours, user, task, comment, time category, billing type (Billable, Non-billable), approval status (Not submitted, Pending, Approved, Rejected).
You set in Pike: Whether rejected time imports at all.
Template columns: date, hours, email, projectNumber, taskTitle, note, billableStatus, approvalStatus
Bill rates and cost rates
Pike: Project hourly rate and cost profiles
Carries over: Account-wide rates per job role and user, and custom rates per project.
You set in Pike: One `hourlyRate` per project, and a cost profile per member from the Wrike cost rate.
Template columns: hourlyRate
Invoices
Pike: Invoice history from accounting
Carries over: Wrike records no invoices. Pike imports them from the ledger your team invoices from.
You set in Pike: Nothing. The CSV route does not import invoices.
On Pinnacle and Apex, Wrike stores a bill rate and a cost rate per job role and per user, with custom rates per project. Pike’s project template takes one `hourlyRate`, so work out the rate each project bills at, and set task rates in Pike where roles bill differently.
Wrike’s Budget field is a money figure entered by hand on the project, so map it to `budgetAmount`. Actual fees and Planned fees are calculated from time and effort, and Pike recalculates them from imported hours and rates.
Wrike applies a cost rate change from the day of the edit forward. Set each member’s Pike cost profile from the current Wrike cost rate before the pilot.
The plan
Seven steps out of Wrike
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
The Excel files are a snapshot. Write down the export date: at cutover you export the timelog after it.
- Pick a cutover Friday after the month’s invoices go out, and confirm the exporting admin is not a Collaborator, Contributor or Viewer.
- Lock the Timelog dates you export where your plan allows it, so nobody edits exported time.
- Export every space, the Timelog view and the user list, and keep the raw files unchanged in one folder.
Done when: Project, timelog and user 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 exported files
Clean the CSV files. Nobody edits Wrike projects or time after export day.
- Give every client space or folder a customer number, and every project a project number and a `billingType`.
- Remove duplicate task rows where a task appears under several projects, and keep the row for the project that bills it.
- Map Billable to `billable`, Non-billable to `nonBillable`, Approved to `approved`, Pending to `submitted`, and Not submitted to `draft`.
Done when: Every open project has a number, a customer number, a billing type, a budget and a rate.
Week 2
Workspace admin
Week 2 · Workspace admin
Build the workspace shell
Admins set up Pike before the first upload, so they can give imported projects a team and a rate on day one.
- Create teams and positions that match your Wrike job roles. Invite admins and project leads only.
- Connect your accounting system and run Import data for customers and invoice history.
- Set a cost profile for each member from their Wrike cost rate.
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
Upload in dependency order
Customers, then projects and phases, then members, then tasks and time. Pike reports a row it cannot match with its line number.
- Download each Pike template and map the Wrike headers with the Wrike column mapping.
- Fix rejected rows and re-upload them. Pike matches on project number, customer number or email and updates the record.
- Compare three projects with Wrike: Budget, Actual fees and last month’s hours.
Done when: Project, user and last-month hour counts match the Wrike Timelog view.
Week 3 to 4
Delivery lead, finance
Week 3 to 4 · Delivery lead, finance
One team in Pike for a sprint
CSV has no ongoing sync, so the pilot team moves fully to Pike while everyone else logs time in Wrike.
- The pilot team logs time in Pike only, from Monday. Everyone else logs time in Wrike until cutover.
- Finance approves pilot time in Time admin and sends one invoice from Pike.
- Compare the pilot project’s margin in Pike with Actual fees and Actual cost in Wrike. A gap means a rate or cost profile needs a fix.
Done when: One invoice sent from Pike. No pilot team time in Wrike after the pilot start date.
Week 4 to 5
Migration owner
Week 4 to 5 · Migration owner
Cutover weekend
Close Wrike on Friday evening and upload the time logged since your first export.
- Friday: everyone submits time and managers approve it. Filter the Timelog view from the day after your first export to Friday, export it and upload those rows.
- Turn off Wrike Integrate recipes for HubSpot and Salesforce, so new deals create no Wrike projects.
- Delete users who no longer need Wrike to free their seats. Deactivated users still take a seat, and deleted users cannot be restored.
Done when: Time admin shows every active member by Monday afternoon. Wrike shows no time 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 Wrike.
- Approve all time, invoice every billable project from Pike, and check each invoice appears in your accounting system.
- Run an Account Backup on Business and above for the archive, before anyone deletes users or projects.
- Contact Wrike support to close a paid account. Wrike deletes a paid account only after its billing period ends, and deletion removes all tasks, folders, files and discussions.
Done when: Month closed in Pike. Final Wrike exports and backup saved with two owners.
Rebuild
Set these up in Pike by hand
- Job role ratesSet bill rates on projects and tasks from your Wrike job role rates.Pike docs
- Cost ratesCreate a cost profile per member from their Wrike cost rate.Pike docs
- BlueprintsRebuild each project blueprint as a Pike project template.Pike docs
- Workload and effortRecreate future effort as allocations in resource planning.Pike docs
- Timelog approvals and lockingChoose who approves time for each team in Time admin.Pike docs
Questions
Moving from Wrike: common questions
Why do some Wrike tasks appear twice in our export?
Wrike exports a task once for each project or folder it is tagged in, and a subtask under the same parent can appear twice with the same Key. Remove the duplicates before upload, or Pike creates one task per row.
Why is our Excel export missing Created Date and ID?
Export Project to Excel leaves out Created Date, Completed Date, ID and formula custom fields. Add those columns to a Table View and use Export this table to Excel.
Does the Timelog export include hidden columns?
Yes. Wrike exports the full timelog table, including columns you hid in the view. Only the filter changes which entries the file includes, so clear it before the full export.
How do Wrike approval statuses map to Pike?
Wrike records Not submitted, Pending, Approved and Rejected on each timelog entry. Map Approved to `approved`, Pending to `submitted` and Not submitted to `draft`, and decide with finance whether rejected time imports.
Can we get our Wrike data as CSV without Excel?
The user list exports as CSV directly. On Pinnacle and Apex, BI Export writes Projects, Tasks, Users and Timelog entries as CSV files in the backup, refreshed once a day.
Wrike documentation used for this guide
- Wrike: Exporting Data to Excel From Wrike
- Wrike: Exporting Timelog View
- Wrike: Exporting a List of Account Users
- Wrike: Export Data from Wrike Efficiently
- Wrike: BI Export in Wrike
- Wrike: Account Backup
- Wrike: Hourly Rates in Wrike’s Budgeting
- Wrike: Financial Fields for Budgeting
- Wrike API: Timelogs
- Wrike: User Deletion vs Deactivation
- Wrike: Close an Account
- Wrike: Wrike and HubSpot Integration
- Wrike: Salesforce Integration Manual
Your business runs better on Pike.
ISO 27001
GDPR
SOC 2 Type II
Built to keep sensitive client data secure and private.