Clients
Pike: Customers
Carries over: Client name, from the Client Name column of the projects file.
You set in Pike: Customer number, VAT ID and currency, from your ledger.
Template columns: customerName, customerNumber
Migration guide
Move from Runn to Pike
Export Runn’s projects, people, assignments and timesheets from the CSV tool, map them to Pike templates, and connect the ledger you invoice from. Budget five to six weeks.
Available now
Runn’s CSV tool under Settings → CSV exports projects, people, assignments and timesheets, and its column names map closely to Pike templates.
- As an admin with Edit Account Settings and Data turned on, open Settings → CSV. On the Projects tab, click Download Existing Projects CSV, and export active people the same way.
- On the Assignments tab, pick a date range from today forward and click Download Assignments CSV. Assignments map to Pike allocations.
- On the Timesheets tab, pick each year you keep and click Download Timesheets CSV. Runn records actuals per day in minutes.
- Upload customers, projects, phases, members, then time entries and allocations under Workspace settings → Integrations → CSV, using the Runn column mapping.
If Runn reads actuals from Harvest or Clockify, import time with Pike’s native Harvest or Clockify integration and skip the timesheets file.
Available now
Runn lists no accounting or CRM integration, so customers and invoice history come from the ledger finance invoices from. Connect that ledger to Pike.
- In Pike, go to Workspace settings → Integrations, add your accounting system and run Import data for customers and invoice history.
- Use the ledger customer number for each Runn Client Name before you upload projects, so every project links to a customer with invoice history.
- From cutover, finance invoices from Pike using approved time, in place of the Runn actuals report.
Runn imports people and time off from HR tools including BambooHR, HiBob, Gusto and Workday. Pike connects to all four, so connect the same HR system to Pike.
Entity map
What each Runn record becomes in Pike
Column one uses Runn’s screen names. Runn calls planned work assignments and logged work actuals, and matches people on **Email**, as Pike does.
Projects
Pike: Projects
Carries over: Project Name, Client Name, Status (Confirmed or Tentative), Primary Team, Pricing Model (Time and Materials, Fixed Price, Non-billable), Rate Card Name, Budget, Project Manager Identifiers, Project ID.
You set in Pike: Project number (reuse the Runn Project ID or an External Reference). Tentative projects become Pike deals.
Template columns: projectNumber, title, customerNumber, billingType, budgetAmount, leadEmail
Phases
Pike: Phases
Carries over: Phase name and Phase ID, referenced by assignments and timesheets.
You set in Pike: Check whether your export includes phase dates.
Template columns: projectNumber, phase, startDate, endDate
People
Pike: Members
Carries over: First Name, Last Name, Email, Default Role Name, Team Name, Cost to Business (per hour), Employment Type, Job Title, Start Date, End Date.
You set in Pike: Workspace role and cost profile.
Template columns: email, displayName, team, position
Assignments
Pike: Allocations
Carries over: Project, person, role, Start Date, End Date, Minutes Per Day, Billable (Y or N), phase, note.
You set in Pike: Multiply minutes per day by working days and divide by 60 for hours per week.
Template columns: email, projectNumber, startDate, endDate, hoursPerWeek
Actuals (timesheets)
Pike: Time entries
Carries over: Person, project, Role Name, Phase ID, Date, Minutes, Billable (Y or N), Note, Person Email.
You set in Pike: Divide minutes by 60. Set `approvalStatus` with finance, since the timesheets file lists no approval column.
Template columns: date, hours, email, projectNumber, note, billableStatus, approvalStatus
Roles and rate cards
Pike: Positions and project hourly rates
Carries over: Default Rate and Default Cost per role, Rate Card Name per project.
You set in Pike: One `hourlyRate` per project from its rate card.
Template columns: position (Members), hourlyRate (Projects)
Time off
Pike: Time off
Carries over: Scheduled leave and public holidays. Runn adds time off by CSV but lists no export.
You set in Pike: Rebuild time off types and book future leave in Pike, or connect the HR system Runn reads leave from.
Runn sets a Default Rate and Default Cost on each role, and a project picks a rate card by Rate Card Name. Pike reads one `hourlyRate` per project, so set it from the rate of the role that logs most hours, and add task rates in Pike where roles bill differently.
Runn stores Cost to Business (per hour) on each person, and falls back to the role’s default cost when it is blank. Build Pike cost profiles from the person value where set.
Runn budgets in money only in the projects file. Fill `budgetAmount` from Budget, and map Time and Materials to `timeAndMaterials`, Fixed Price to `fixedFee` and Non-billable to `nonBillable`.
The plan
Seven steps out of Runn
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 files you export in week one are what Pike imports. Freeze edits in Runn before you export.
- Download the projects and people files, the assignments from today forward, and the timesheets one year per file.
- The projects file lists active projects only, while the timesheets file covers archived projects too. List the archived Project IDs in the timesheets file and add those projects by hand.
- Write down the export date and keep the raw files unchanged in one folder with two owners.
Done when: Every Runn export 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
Work in copies of the Runn files. Most of the work is minutes, pricing models and Tentative projects.
- Build one customer row per Client Name with a ledger customer number, and add it to every project row.
- Map each Pricing Model to `billingType`, and move Tentative projects to the deals file.
- Divide timesheet minutes by 60, and turn each assignment’s minutes per day into hours per week.
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
Build the workspace shell
Admins set up Pike before the first upload, so imported projects have a team and a rate on day one.
- Create teams and positions from Runn’s Team Name and Default Role Name values. Invite admins and project managers only.
- Connect the ledger finance invoices from and run Import data for customers and invoice history.
- Set a cost profile for each person from Cost to Business (per hour), or the role default cost where blank.
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
Upload in dependency order
Upload under Workspace settings → Integrations → CSV. Pike reports a row it cannot match with its line number.
- Upload customers, projects, phases and members, then timesheets one file per year, then assignments as allocations.
- Fix rejected rows and upload them again. Pike matches each row on its project number or email and updates the record.
- Compare three projects with Runn: budget, rate, last month’s actuals and next month’s assigned hours.
Done when: Project, person, last-month actual hours and next-month assigned hours match Runn.
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 plans and logs in Pike while everyone else works in Runn.
- The pilot team logs time and books allocations in Pike only. Everyone else works in Runn until cutover.
- Finance approves pilot time in Time admin and sends one invoice from Pike.
- Compare the pilot team’s utilization in Pike with Runn’s People Explorer for the same weeks.
Done when: One invoice sent from Pike. Pilot hours in Pike match Runn actuals.
Week 4 to 5
Migration owner
Week 4 to 5 · Migration owner
Cutover weekend
Close Runn on Friday evening and upload every hour recorded there since your first export.
- Friday: download timesheets from your first export date to Friday and assignments from Monday forward, leave out the pilot team, and upload both.
- Set a contract end date for each person, remove future assignments, then archive them. Runn retains their data.
- Under Settings → Plan & Billing, click Edit and remove the freed resource seats. Archiving does not reduce Runn’s billing on its own.
Done when: Time admin shows every active member by Monday afternoon. Runn shows no actuals 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 Runn.
- Approve all time, invoice every billable project from Pike, and check each invoice appears in your ledger.
- Export every CSV once more for the archive.
- Cancel under Settings → Plan & Billing → Cancel Subscription on a monthly plan, or email success@runn.io on an annual plan. Runn retains the data for 12 months in case you reactivate.
Done when: Month closed in Pike. Final Runn exports saved with two owners. Runn subscription cancelled.
Rebuild
Set these up in Pike by hand
- Rate cardsSet project and task rates in Pike from each Runn rate card.Pike docs
- Cost to BusinessCreate a cost profile per member from the Runn cost.Pike docs
- Tentative projectsCreate them as deals with value and expected close date.Pike docs
- Future assignmentsCheck imported allocations in resource planning.Pike docs
- Time offSet up time off types and book future leave.Pike docs
Questions
Moving from Runn: common questions
Why are archived projects missing from our projects file?
Runn’s projects export lists active projects only. The assignments and timesheets exports cover active and archived projects, so take archived project IDs from those files and add the projects by hand.
Who can use the Runn CSV tool?
Only admins with Edit Account Settings and Data set to on. Ask a Runn admin to run every export on the same day.
How do Runn minutes become Pike hours?
Runn records timesheets as minutes per day and assignments as minutes per day. Divide timesheet minutes by 60 for `hours`, and multiply assignment minutes by working days, then divide by 60, for `hoursPerWeek`.
Our Runn actuals come from Harvest. What do we import?
Runn syncs Harvest and Clockify timesheets into Runn once a day. Pike has native Harvest and Clockify integrations, so import time from the source and use the Runn files for projects, people and assignments.
What happens to our Runn data after we cancel?
Runn ends the subscription at the close of the billing cycle and retains your data for 12 months, and integrations stop. Deleting the account is a separate step.
Runn documentation used for this guide
- Runn: CSV import and export overview
- Runn: Import/Export Projects
- Runn: Import/Export Timesheets
- Runn: Import/Export Assignments
- Runn: Data format and requirements for CSV tool
- Runn: Archive/Unarchive People
- Runn: How do I add or remove resource seats?
- Runn: How do I cancel my Runn account?
- Runn: Integrations, time tracking tools
- Runn: Integrations and API
- Runn: Integrations
- Runn API
Your business runs better on Pike.
ISO 27001
GDPR
SOC 2 Type II
Built to keep sensitive client data secure and private.