Clients
Pike: Customers
Carries over: Client name and the projects billed to it.
You set in Pike: Nothing.
Template columns: customerName

Migration guide
Connect Ajera through an API user, 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 Ajera through the Ajera API, so clients, projects with their phases, employees, timesheet entries and invoices import with their links intact.
Pike never writes to Ajera, so leave Can Write off on the API user. A project removed in Ajera shows as Removed in Ajera in Pike, with its history intact.
Available now
Use CSV when no Ajera administrator can set up an API user, or when you bring over only part of your history.
Native sync is the only route that imports Ajera invoices, phase budgets and hourly rates with their project links.
Entity map
Column one uses Ajera's own labels. Pike matches people on the email of each Ajera employee.
Pike: Customers
Carries over: Client name and the projects billed to it.
You set in Pike: Nothing.
Template columns: customerName
Pike: Projects
Carries over: Project ID, description, billing type, budget and hourly rates.
You set in Pike: Team and project template.
Template columns: projectNumber, title, customerNumber, billingType, budgetAmount, budgetHours, hourlyRate
Pike: Phases
Carries over: Phase name and budget, under the matching project.
You set in Pike: Start and end dates.
Template columns: projectNumber, phase, startDate, endDate
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, project, notes and billable flag.
You set in Pike: Approval. Pike’s Ajera import lists notes and the billable flag, and no supervisor or accounting approval, so approve open weeks in Time admin.
Template columns: date, hours, email, projectNumber, taskTitle, note, billableStatus
Pike: Invoice history (read-only)
Carries over: Invoices on each project.
You set in Pike: New invoices go out from Pike from cutover.
Pike: Not imported
Carries over: Activity on each timesheet line, such as Billable Time or Meetings.
You set in Pike: Labels, if you report on activity today.
Ajera bills Time & Expense projects from a billing rate table. When the table has no rate, Ajera multiplies the cost rate by the table’s markup. Pike imports the hourly rates on each project, so compare one project per rate table after the import.
Ajera has fee-based billing types (Fixed Fee, Percent Complete, Unit Price, Percent of Construction Cost) and Nonbillable, Marketing and Overhead. Pike has fixed fee, time and materials and non-billable, so check the type on every Percent Complete and Unit Price project.
Phase budgets import under each project. Pike’s Ajera import lists no cost rates, so set a cost profile for each member from the Ajera pay rate before the pilot.
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 Ajera directly. The export in week one is your archive copy.
Done when: Archive exports in one folder, a cutover Friday on the calendar, and an Ajera administrator named to create the API user.
Week 1 to 2
Operations lead
Week 1 to 2 · Operations lead
Pike imports what Ajera stores, so fix clients, phases and employee emails inside Ajera before you click Import data.
Done when: No duplicate clients. Every active project has a billing type, a rate table and phase budgets.
Week 2
Workspace admin, finance
Week 2 · Workspace admin, finance
Ajera includes general ledger and payroll, so decide which accounting system takes over before you build anything else.
Done when: Admins and leads are in Pike. Finance sees the same client list as Ajera.
Week 2 to 3
Workspace admin
Week 2 to 3 · Workspace admin
One click imports clients, projects, phases, employees, timesheet entries and invoices in dependency order.
Done when: Client, project, phase, employee and last-month hour counts match Ajera.
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 hours in Pike match the same week in Ajera.
Week 4 to 5
Migration owner
Week 4 to 5 · Migration owner
Close Ajera timesheets on Friday evening. Finance continues to post in Ajera, so nobody else needs to open it from Monday.
Done when: Time admin shows every active member by Monday afternoon. Ajera shows no timesheets after Friday.
Week 5 to 8
Finance
Week 5 to 8 · Finance
Done when finance closes a month without opening Ajera for projects or time.
Done when: Month closed in Pike. Ajera exports saved with two owners. Deltek exit date agreed.
Rebuild
Questions
Read access to clients, projects and employees, and an active authorizing employee, which Ajera’s timesheet API requires. Pike never writes to Ajera, so leave Can Write off.
Each Ajera phase imports as a Pike phase with its budget, under the matching project. Check phase budgets and hours on two projects against the Ajera Project inquiry after the import.
Pike’s project billing types are fixed fee, time and materials and non-billable. Set Percent Complete and Unit Price projects to fixed fee with the contract amount as budget, and invoice progress from Pike.
No. Pike covers projects, time and invoicing, and imports Ajera invoices as read-only history. Pick the ledger that takes over general ledger and payroll before cutover, and connect it to Pike.
The Timesheet Detail export includes only the columns the inquiry shows, one row per line with seven day columns. The Ajera API returns each timesheet with its project entries, daily hours and notes, so Native sync needs no reshaping of day columns.
ISO 27001
GDPR
SOC 2 Type IIBuilt to keep sensitive client data secure and private.