Customers
Pike: Customers
Carries over: Customer name and the fields in the module grid, from Download Excel.
You set in Pike: Customer number, currency and VAT ID.
Template columns: customerName, customerNumber, taxVatId, mainCurrency

Migration guide
Export AdaptiveWork modules and reports to Excel, save them as CSV, and upload them to Pike templates. Budget five to six weeks to cutover.
Available now
AdaptiveWork exports the Customers and Users modules and each project work plan to Excel, and any report to Excel, so you export each entity, save it as CSV and map it to a Pike template.
For a full extract, AdaptiveWork offers a Data Warehouse Export extension and the REST API version 2. Ask your AdaptiveWork administrator which one your org has enabled.
Available now
AdaptiveWork connects to Salesforce through its iHub platform, as a paid extension. Its help centre documents no accounting integration, so connect Pike to the accounting system your finance team already invoices from.
Turn off the iHub Salesforce events in AdaptiveWork at cutover, so only Pike reads opportunities from then on.
Entity map
Column one uses AdaptiveWork labels. Projects, milestones and tasks are all work items, and only work items marked reportable appear on timesheets. Pike matches people on each user’s email.
Pike: Customers
Carries over: Customer name and the fields in the module grid, from Download Excel.
You set in Pike: Customer number, currency and VAT ID.
Template columns: customerName, customerNumber, taxVatId, mainCurrency
Pike: Projects
Carries over: Name, customer, project manager, Billing Type (Fixed Price, Time & Materials, Milestone), state, Expected Revenue, Budgeted Cost and dates.
You set in Pike: Project number and one billing type per project.
Template columns: projectNumber, title, customerNumber, status, billingType, budgetAmount, budgetHours, startDate, endDate, leadEmail
Pike: Phases
Carries over: Milestone name and due date from the work plan export.
You set in Pike: A start date for each phase.
Template columns: projectNumber, phase, startDate, endDate
Pike: Tasks
Carries over: Title, parent, assigned resources, dates, work and the reportable flag from the work plan export.
You set in Pike: Billable status per task.
Template columns: title, projectNumber, phase, assigneeEmail, startDate, dueDate, status, billableStatus
Pike: Members
Carries over: Name, email, job title and state (Active, Pending, Suspended or Deleted).
You set in Pike: Workspace role, team and a cost profile.
Template columns: email, displayName, team, position
Pike: Positions and project hourly rates
Carries over: Job title billing rates with effective dates, and rate cards with versions of job title billing rates for customer projects.
You set in Pike: One `hourlyRate` per project, from the rate card version in force on that project.
Template columns: position (Members), hourlyRate (Projects)
Pike: Cost profiles
Carries over: Date-effective cost rates on each user under Related Items → Rates. Rate cards store no cost rates.
You set in Pike: A cost profile for every member who logs time, from their current cost rate.
Pike: Time entries
Carries over: Work item, user, date, duration and approval state (Unsubmitted, Submitted or Approved) from a timesheet report.
You set in Pike: Map Approved to `approved`, Submitted to `submitted`, and Unsubmitted to `draft`.
Template columns: date, hours, email, projectNumber, taskTitle, note, billableStatus, approvalStatus
Pike: Expenses
Carries over: Project expenses and billable expenses. Check whether your report includes the user and expense type.
You set in Pike: Nothing.
Template columns: date, amount, projectNumber, email, category, description, billableStatus
Pike: Allocations
Carries over: Assigned resources and work per task. Check whether your report includes hours per week.
You set in Pike: Convert each assignment to hours per week before upload.
Template columns: email, projectNumber, startDate, endDate, hoursPerWeek
AdaptiveWork prices work from job title billing rates, user rates and rate cards, each with effective dates, and a project can override rates. Pike reads one `hourlyRate` per project, so take the rate from the rate card version in force on each open project.
AdaptiveWork sets cost rates per user with from and to dates, and rate cards store no cost rates. Set each Pike cost profile from the user’s current cost rate, and compare margin on older months with AdaptiveWork where a rate changed.
AdaptiveWork calculates Expected Revenue and Budgeted Cost from work and rates, or from a manual Fixed Cost or Total Estimated Cost. Fill `budgetAmount` from Expected Revenue, and map Fixed Price and Milestone projects to `fixedFee` and Time & Materials to `timeAndMaterials`.
The plan
The same steps as the main migration guide, with this tool's screens and settings.
Week 1
Migration owner, AdaptiveWork administrator
Week 1 · Migration owner, AdaptiveWork administrator
The files you export in week one are what Pike imports. Freeze edits in AdaptiveWork before you export.
Done when: Module, work plan and report files in one folder, the export date written down, and a cutover Friday on the calendar.
Week 1 to 2
Operations lead
Week 1 to 2 · Operations lead
Work in copies of the AdaptiveWork files and keep the raw folder untouched. Rename columns to Pike template columns as you go.
Done when: Every project row has a project number, a customer number, a billing type and a budget amount.
Week 2
Workspace admin
Week 2 · Workspace admin
Admins set up Pike before the first upload, so imported projects have a lead and imported members have a team.
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
Upload under Workspace settings → Integrations → CSV. Pike reports a missing customer number, project number or email with its line number.
Done when: Customer, project, user and last-month hour counts match AdaptiveWork.
Week 3 to 5
Delivery lead, finance
Week 3 to 5 · Delivery lead, finance
The CSV route has no ongoing sync. The pilot team logs time in Pike only, and everyone else fills in AdaptiveWork timesheets until cutover.
Done when: One invoice sent from Pike. The pilot lead signs off.
Week 5 to 6
Migration owner
Week 5 to 6 · Migration owner
Close AdaptiveWork timesheets on Friday evening and upload every hour logged there since your first export.
Done when: Time admin shows every active member by Monday afternoon. AdaptiveWork shows no time after Friday.
Week 6 to 9
Finance
Week 6 to 9 · Finance
Done when finance closes a month without opening AdaptiveWork.
Done when: Month closed in Pike. AdaptiveWork exports saved with two owners. License change agreed.
Rebuild
Questions
AdaptiveWork emails Excel exports between 100,000 and 999,970 rows and does not offer them for download. Split the report by date range so each export has fewer than 100,000 rows.
Timesheets list only work items flagged as reportable. People cannot log time on other work items, so check the flag on tasks you expected to see.
An Excel export includes the report highlights and the results grid, without charts. Pike needs only the grid, so export to Excel and save the file as CSV.
Suspending a user removes login access and retains the license allocated to them. Deleting removes the user from the resource pool, retains their assignments and shows the name with a strikethrough, and an admin can restore them later.
Pike has no CSV template for invoices, and the AdaptiveWork help centre documents no invoicing. Pike imports invoice history from the accounting system you connect.
ISO 27001
GDPR
SOC 2 Type IIBuilt to keep sensitive client data secure and private.