Customers
Pike: Customers
Carries over: Customer name and the jobs under it.
You set in Pike: Nothing.
Template columns: customerName

Migration guide
Connect WorkBook with an API key, run Import data, and keep 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 WorkBook through its REST API, so customers, jobs, tasks, employees, time entries, invoices and resource bookings import with their links intact.
Pike never writes to WorkBook. WorkBook caps an API key at three months from creation, so note the expiry date and generate a new key before it lapses during the parallel run.
Available now
Use CSV when no System Administrator can issue an API key, or when you bring over only part of your history.
Native sync is the only route that imports WorkBook invoices and resource bookings with their job links. On CSV, rebuild bookings as Pike allocations by hand.
Entity map
Column one uses WorkBook's own labels. Pike matches people on the email of each WorkBook employee.
Pike: Customers
Carries over: Customer name and the jobs under it.
You set in Pike: Nothing.
Template columns: customerName
Pike: Projects
Carries over: Job name, customer, fixed price or time and materials, budget and hourly rates.
You set in Pike: Team and project template.
Template columns: projectNumber, title, customerNumber, billingType, budgetAmount, hourlyRate
Pike: Tasks
Carries over: Task name under each job.
You set in Pike: Phases. WorkBook groups tasks into schedules and phases on a job, and Pike’s import lists tasks only.
Template columns: title, projectNumber
Pike: Members
Carries over: Name and email.
You set in Pike: Workspace role, team, position and cost profile.
Template columns: email, displayName
Pike: Time entries
Carries over: Date, hours, notes, billable flag and invoiced status.
You set in Pike: Nothing.
Template columns: date, hours, email, projectNumber, taskTitle, note, billableStatus, invoiced
Pike: Invoice history (read-only)
Carries over: Invoices on each job, as read-only history.
You set in Pike: New invoices go out from Pike from cutover.
Pike: Allocations
Carries over: Booked employee, job and hours, when Import bookings is on.
You set in Pike: Bookings still waiting for approval in WorkBook.
Template columns: email, projectNumber, startDate, endDate, hoursPerWeek
Pike reads the billing type of each job (fixed price or time and materials), its budget and its hourly rates. Teams manage WorkBook price lists from the Jobs List, so open one job per price list after the import and compare its rates.
The WorkBook Job value statement report shows approved price quotes and work in progress on open jobs. Compare its totals with the budgets Pike imports for your largest open jobs.
Pike’s WorkBook import lists no cost rates. Set a cost profile for each member before the pilot, so the Finance tab shows margin on the first imported month.
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 WorkBook 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 System Administrator named to issue the API key.
Week 1 to 2
Operations lead
Week 1 to 2 · Operations lead
Pike imports what WorkBook stores, so merge customers and fix employee emails inside WorkBook before you click Import data.
Done when: No duplicate customers. Every open job has a billing type, a budget and a price list.
Week 2
Workspace admin, finance
Week 2 · Workspace admin, finance
WorkBook includes Finance & Administration as well as jobs, so decide which ledger takes over posting before you build anything else.
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 customers, jobs, tasks, employees, time, invoices and bookings in dependency order.
Done when: Customer, job, employee and last-month hour counts match WorkBook.
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 job and an invoice due.
Done when: One invoice sent from Pike. Pilot hours in Pike match the same week in WorkBook.
Week 4 to 5
Migration owner
Week 4 to 5 · Migration owner
Close WorkBook time entry on Friday evening. Narrow access in User Access Rights in place of a read-only mode.
Done when: Time admin shows every active member by Monday afternoon. WorkBook shows no time after Friday.
Week 5 to 8
Finance
Week 5 to 8 · Finance
Done when finance closes a month without opening WorkBook.
Done when: Month closed in Pike. WorkBook exports saved with two owners. Deltek exit date agreed.
Rebuild
Questions
Use an API-Only user. Deltek recommends them for integrations unless the integration needs to act as an administrator, and Pike only reads from WorkBook. A System Administrator generates the key on the API Key Setup tab.
Yes. Pike imports the invoiced status on each time entry, and WorkBook invoices as read-only history. Those hours show as invoiced and never appear on a new Pike invoice.
Yes. Turn on Import bookings and Pike imports WorkBook resource bookings as allocations. WorkBook books resources on tasks, so check each allocation is on the right Pike project after the import.
WorkBook sets every API key to expire within three months of creation. Generate a new key on the API Key Setup tab and enter it on the Deltek WorkBook integration page in Pike.
WorkBook Data Export runs per company: pick each company in the drop-down above the left pane and archive its files separately. Give the API-Only user access to every company you migrate, then compare customer counts per company after the import.
ISO 27001
GDPR
SOC 2 Type IIBygget til at holde følsomme klientdata sikre og private.