Pike
  • Pricing
  • Contact us
Log in
  1. Home/
  2. Migration guide/
  3. Planview AdaptiveWork
Planview AdaptiveWork logoPike logo

Migration guide

Move from Planview AdaptiveWork to Pike

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.

  1. 1Open the Customers module, then the People module, and click Utilities → Export → Download Excel in each.
  2. 2In Reports, click New → Report, set Report On to projects, add the fields in the column mapping and click Export → Excel. Repeat for timesheet entries, one date range per export: reports over 100,000 rows can be emailed but not downloaded.
  3. 3For tasks and milestones, open each project and use Utilities → Export Workplan. Save every file as CSV UTF-8.
  4. 4Upload customers, projects, phases, members, tasks, then time entries and expenses under Workspace settings → Integrations → CSV, using the Planview AdaptiveWork column mapping.

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.

  1. 1In Pike, go to Workspace settings → Integrations, add the accounting system finance invoices from and run Import data for customers and invoice history.
  2. 2If AdaptiveWork syncs with Salesforce today, add Salesforce to Pike, so Pike imports customers, contacts and deals from the same org.
  3. 3Give each Pike customer the customer number your AdaptiveWork project file uses before you upload projects.

Turn off the iHub Salesforce events in AdaptiveWork at cutover, so only Pike reads opportunities from then on.

Entity map

What each Planview AdaptiveWork record becomes in Pike

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.

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

Projects

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

Milestones

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

Tasks (work items)

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

Users

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

Job Titles and Rate Cards

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)

User cost rates

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.

Timesheets

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

Expenses

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

Resource assignments

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

Planview AdaptiveWork entityPike entityWhat carries overWhat you set in PikeTemplate columns
CustomersCustomersCustomer name and the fields in the module grid, from Download Excel.Customer number, currency and VAT ID.customerName, customerNumber, taxVatId, mainCurrency
ProjectsProjectsName, customer, project manager, Billing Type (Fixed Price, Time & Materials, Milestone), state, Expected Revenue, Budgeted Cost and dates.Project number and one billing type per project.projectNumber, title, customerNumber, status, billingType, budgetAmount, budgetHours, startDate, endDate, leadEmail
MilestonesPhasesMilestone name and due date from the work plan export.A start date for each phase.projectNumber, phase, startDate, endDate
Tasks (work items)TasksTitle, parent, assigned resources, dates, work and the reportable flag from the work plan export.Billable status per task.title, projectNumber, phase, assigneeEmail, startDate, dueDate, status, billableStatus
UsersMembersName, email, job title and state (Active, Pending, Suspended or Deleted).Workspace role, team and a cost profile.email, displayName, team, position
Job Titles and Rate CardsPositions and project hourly ratesJob title billing rates with effective dates, and rate cards with versions of job title billing rates for customer projects.One `hourlyRate` per project, from the rate card version in force on that project.position (Members), hourlyRate (Projects)
User cost ratesCost profilesDate-effective cost rates on each user under Related Items → Rates. Rate cards store no cost rates.A cost profile for every member who logs time, from their current cost rate.
TimesheetsTime entriesWork item, user, date, duration and approval state (Unsubmitted, Submitted or Approved) from a timesheet report.Map Approved to `approved`, Submitted to `submitted`, and Unsubmitted to `draft`.date, hours, email, projectNumber, taskTitle, note, billableStatus, approvalStatus
ExpensesExpensesProject expenses and billable expenses. Check whether your report includes the user and expense type.Nothing.date, amount, projectNumber, email, category, description, billableStatus
Resource assignmentsAllocationsAssigned resources and work per task. Check whether your report includes hours per week.Convert each assignment to hours per week before upload.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

Seven steps out of Planview AdaptiveWork

The same steps as the main migration guide, with this tool's screens and settings.

  1. Week 1

    Migration owner, AdaptiveWork administrator

    1

    1Week 1 · Migration owner, AdaptiveWork administrator

    Freeze scope and export

    The files you export in week one are what Pike imports. Freeze edits in AdaptiveWork before you export.

    • Run Download Excel in the Customers and People modules, and Export Workplan on each open project.
    • Build one report on projects and one on timesheets, and export each to Excel in date ranges under 100,000 rows.
    • Save every file as CSV UTF-8, and write down the date of your first export.
    exports / rawdo not edit
    • customers.csvraw
    • projects.csvraw
    • tasks.csvraw
    • time-entries.csvraw
    • invoices.csvraw
    Cutover: Friday, week 5

    Done when: Module, work plan and report files in one folder, the export date written down, and a cutover Friday on the calendar.

  2. Week 1 to 2

    Operations lead

    2

    2Week 1 to 2 · Operations lead

    Clean the exported files

    Work in copies of the AdaptiveWork files and keep the raw folder untouched. Rename columns to Pike template columns as you go.

    • Build one customer row per AdaptiveWork customer with a `customerNumber`, and add it to every project row.
    • Split each work plan: projects to the projects file, milestones to phases, and tasks to the tasks file.
    • Check every user email against the address they will sign in to Pike with. Pike matches members, time and allocations on `email`.
    customers.csvbefore / after
    • Acme
    • ACME Ltd
    • Acme retainer

    Acme

    C-104 · T&M · 1,250/h

    Done when: Every project row has a project number, a customer number, a billing type and a budget amount.

  3. Week 2

    Workspace admin

    3

    3Week 2 · Workspace admin

    Build the workspace shell

    Admins set up Pike before the first upload, so imported projects have a lead and imported members have a team.

    • Create teams that match your AdaptiveWork groups and positions that match your job titles. Invite admins and project leads only.
    • Connect the accounting system finance invoices from and run Import data.
    • Set a cost profile for each member from their current AdaptiveWork cost rate.
    Workspace setup
    • Teams and roles
    • Templates and labels
    • Cost profiles12 of 12
    • Accounting connected
    • Invite everyoneweek 4

    Done when: Admins and leads are in Pike. Finance sees the same customer list as the ledger.

  4. Week 2 to 3

    Workspace admin

    4

    4Week 2 to 3 · Workspace admin

    Upload in dependency order

    Upload under Workspace settings → Integrations → CSV. Pike reports a missing customer number, project number or email with its line number.

    • Upload customers, projects, phases, members and tasks, then time entries, expenses and allocations.
    • Fix rejected rows and upload them again. Pike matches each row on its project number or email and updates the record.
    • Open one Fixed Price and one Time & Materials project and compare expected revenue, rate and last month’s hours with AdaptiveWork.
    Import datain order
    • Customers48
    • Projects112
    • Members19
    • Tasks1,430
    • Time entries
    • Deals

    Done when: Customer, project, user and last-month hour counts match AdaptiveWork.

  5. Week 3 to 5

    Delivery lead, finance

    5

    5Week 3 to 5 · Delivery lead, finance

    One team in Pike, the rest in AdaptiveWork

    The CSV route has no ongoing sync. The pilot team logs time in Pike only, and everyone else fills in AdaptiveWork timesheets until cutover.

    • Pick one team with a live client project and an invoice due. From Monday its members log time in Pike only.
    • Finance approves the pilot team’s time in Time admin and sends one invoice from Pike.
    • Compare the pilot project’s actual revenue and cost in Pike with AdaptiveWork. A gap means a rate card or cost rate needs a fix in Pike.

    Old tool

    Rest of team

    logs as before

    keep syncing

    Pike

    Pilot team

    approved, invoiced

    Done when: One invoice sent from Pike. The pilot lead signs off.

  6. Week 5 to 6

    Migration owner

    6

    6Week 5 to 6 · Migration owner

    Cutover weekend

    Close AdaptiveWork timesheets on Friday evening and upload every hour logged there since your first export.

    • Friday: everyone submits, and managers approve the week in the Approvals module.
    • Export the timesheet report from your first export date to Friday, map it to the time entries template and upload it. Leave out the pilot team.
    • Delete users who now log time in Pike. AdaptiveWork removes them from the resource pool and retains their past assignments, shown with a strikethrough.

    Fri

    Approve. Sync. Read-only.

    Sat, Sun

    Rest.

    Mon

    All in Pike. Demo at 10:00.

    Done when: Time admin shows every active member by Monday afternoon. AdaptiveWork shows no time after Friday.

  7. Week 6 to 9

    Finance

    7

    7Week 6 to 9 · Finance

    First month-end in Pike

    Done when finance closes a month without opening AdaptiveWork.

    • Approve all time, invoice every billable project from Pike and send the invoices to accounting.
    • Export the project and timesheet reports once more and store the files with the raw exports.
    • Once the first Pike invoices are paid, agree license changes with your Planview account team.
    Baselinebefore / Pike
    Days to invoice
    Unbilled hours at close
    Margin by project

    Done when: Month closed in Pike. AdaptiveWork exports saved with two owners. License change agreed.

Rebuild

Set these up in Pike by hand

  • Rate cards and job title ratesSet the hourly rate on each project.Pike docs
  • User cost ratesEnter each member’s cost in their cost profile.Pike docs
  • Project templatesRebuild your standard work plans as Pike templates.Pike docs
  • Timesheet approversChoose who approves time for each team in Time admin.Pike docs

Questions

Moving from Planview AdaptiveWork: common questions

Why can’t we download our large timesheet report?

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.

Why are some tasks missing from our timesheet data?

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.

Does the Excel export include charts?

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.

Should we suspend or delete users who leave?

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.

Can Pike import AdaptiveWork invoices?

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.

Support through the move and after it

Migration support comes with every plan: we map your exports, run the imports with you and check the counts before cutover. After go-live, hypercare until the first month-end closes in Pike. Then we hand over to your admins and stay close for as long as you use Pike. Email hello@usepike.com with your source tool and we will say which route fits.

  • Switch playbook
  • Migration guide for every tool

Planview AdaptiveWork documentation used for this guide

  • Planview AdaptiveWork: Creating and Using Reports
  • Planview AdaptiveWork: Importing and Updating Data Using MS Excel
  • Planview AdaptiveWork: Billing types supported in AW
  • Planview AdaptiveWork: Cost and Billing Rates: Date Effective Rates
  • Planview AdaptiveWork: Rate Cards
  • Planview AdaptiveWork: Project Budget
  • Planview AdaptiveWork: Timesheets Overview
  • Planview AdaptiveWork: Timesheet Approvals
  • Planview AdaptiveWork: What are User states?
  • Planview AdaptiveWork: Delete or suspend a user
  • Planview AdaptiveWork: Salesforce Integration
  • Planview AdaptiveWork: Data Warehouse Export
  • Planview AdaptiveWork: REST API Guide Version 2

Your business runs better on Pike.

Contact sales
  • ISO 27001 CertifiedISO 27001
  • GDPR CompliantGDPR
  • AICPA SOC 2 Type IISOC 2 Type II

Built to keep sensitive client data secure and private.

Pike box logoPike
Features
ProjectsResourcing & capacityFinance & invoicingDashboardsCustomers & salesTime & absencePike MCPIntegrations
Company
BlogOur storySwitch playbookMigration guideGet in touch
Industries
Creative agenciesMarketing agenciesDigital agenciesConsulting firmsIT consultanciesArchitecture firms
Resources
DocsChangelogPrivacy policyTerms and conditionsGlossaryFree toolsFAQ
All systems operational

Engineered around the 🌎

© 2026 Pike. All rights reserved.