Clients
Pike: Customers
Carries over: Name, address, currency, archived state.
You set in Pike: Customer number and VAT ID. The Harvest client record holds neither.
Template columns: customerName, mainCurrency

Migration guide
Connect Harvest, run Import data, and keep Harvest syncing while teams move one at a time. Budget five weeks from connection to cutover, then one month-end in Pike.
Available now
Pike reads Harvest through the Harvest API, so clients, projects, rates, time and invoices import with their links intact.
Pike never writes to Harvest. A client or project deleted in Harvest shows as Removed in Harvest in Pike, with its history intact.
Available now
Use CSV when no Harvest administrator can authorize Pike, or when you bring over only part of your history.
Harvest's help centre lists no screen export for task and person rates per project. Check whether your project export includes them, or use Native sync, which reads them through the Harvest API.
Entity map
Column one uses Harvest's own labels. Pike matches people on the email of each Harvest user.
Pike: Customers
Carries over: Name, address, currency, archived state.
You set in Pike: Customer number and VAT ID. The Harvest client record holds neither.
Template columns: customerName, mainCurrency
Pike: Customer contacts
Carries over: First and last name, title, email, office and mobile phone.
You set in Pike: Nothing.
Template columns: customerNumber, name, email, title, phone
Pike: Projects
Carries over: Name, code, client, project type (Time & Materials, Fixed Fee or Non-Billable), fee, budget, start and end dates, notes, archived state.
You set in Pike: Team, phases and project template.
Template columns: projectNumber, title, customerNumber, billingType, budgetAmount, budgetHours, hourlyRate, startDate, endDate
Pike: Tasks
Carries over: Task name, billable flag on each project, hourly rate when the project bills by Tasks, task budget.
You set in Pike: Assignees and status. Harvest tasks hold neither.
Template columns: title, projectNumber, billableStatus
Pike: Members
Carries over: Email, name, contractor flag, default billable rate, cost rate, weekly capacity, rate per project.
You set in Pike: Workspace role, team and position.
Template columns: email, displayName
Pike: Time entries
Carries over: Date, hours, notes, billable flag, billed flag with the Harvest invoice number, approval status (unsubmitted, submitted, approved), the cost rate on the entry.
You set in Pike: Nothing.
Template columns: date, hours, email, projectNumber, taskTitle, note, billableStatus, approvalStatus, invoiced
Pike: Expenses
Carries over: Date, amount, expense category, billable flag, approval status, receipt link.
You set in Pike: Nothing.
Template columns: date, amount, projectNumber, email, category, billableStatus
Pike: Invoice history (read-only)
Carries over: Number, client, state (draft, open, paid, closed), line items.
You set in Pike: New invoices go out from Pike from cutover.
Pike: Allocations
Carries over: Person, client, project and hours per week.
You set in Pike: Member names that differ between Forecast and Pike.
Template columns: email, projectNumber, startDate, endDate, hoursPerWeek
Harvest sets one Bill by option per project: Project, Tasks or People. Pike reads the hourly rate from that level, so a project billed by People brings each person’s project rate, or their default rate where the project uses default rates.
Hours Per Project, Hours Per Task and Hours Per Person import as hour budgets. Total Project Fees and Fees Per Task import as money budgets, and monthly budgets as budgets that reset each month.
Each Harvest time entry records the cost rate in force when it was logged. Pike stores that rate on the entry and sets the member’s cost profile from the current Harvest cost rate, so margin on past months matches Harvest.
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
On Native sync Pike reads Harvest directly. The export in week one is your archive copy.
Done when: Archive exports in one folder, a cutover Friday on the calendar, and a Harvest administrator named to authorize Pike.
Week 1 to 2
Operations lead
Week 1 to 2 · Operations lead
Pike imports what Harvest holds, so merge and fill in inside Harvest before you click Import data.
Done when: No duplicate clients. Every active project has a code, a project type and a budget.
Week 2
Workspace admin
Week 2 · Workspace admin
Admins set up Pike first, so they can give imported projects a team on day one.
Done when: Admins and leads are in Pike. Finance sees the same customer list as the ledger.
Week 2 to 3
Workspace admin
Week 2 to 3 · Workspace admin
One click imports clients, projects, users and time in dependency order.
Done when: Client, project, user and last-month hour counts match Harvest.
Week 3 to 4
Delivery lead, finance
Week 3 to 4 · Delivery lead, finance
Turn on Keep syncing and move one team with a live client project and an invoice due.
Done when: One invoice sent from Pike. Pilot time in Pike matches the same week in Harvest.
Week 4 to 5
Migration owner
Week 4 to 5 · Migration owner
Close Harvest on Friday evening. Archive projects and people in Harvest in place of a read-only mode.
Done when: Time admin shows every active member by Monday afternoon. Harvest shows no time after Friday.
Week 5 to 8
Finance
Week 5 to 8 · Finance
Done when finance closes a month without opening Harvest.
Done when: Month closed in Pike. Harvest data file saved with two owners. Harvest account closed.
Rebuild
Questions
Yes. Pike imports the billed flag and the Harvest invoice number on each time entry. Those hours show as invoiced and never appear on a new Pike invoice.
Harvest locks entries once they are approved or invoiced. Pike imports the approval status, so approved Harvest time is approved in Pike and needs no second approval.
Yes. Harvest says Forecast has no public API, so Pike reads the Projects schedule export from Forecast when Import Forecast is on. Pike matches people by name, so fix any name that differs between Forecast and Pike first.
Pike imports the currency set on each Harvest client and project. Harvest relabels amounts without converting them, so check totals on those clients after the import.
A Pike workspace admin adds the integration and a Harvest administrator signs in to authorize it. With an administrator login, Pike reads every project, rate and cost rate.
ISO 27001
GDPR
SOC 2 Type IIBuilt to keep sensitive client data secure and private.