> ## Documentation Index
> Fetch the complete documentation index at: https://usepike.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Deltek Ajera

> How to import clients, projects, phases, employees, and timesheet entries from Deltek Ajera into Pike, with optional ongoing sync.

The Deltek Ajera integration imports clients, projects with their phases, employees, and timesheet entries from Ajera into Pike, with optional ongoing sync while your team switches over.

## Connect Ajera

1. In Ajera, create an API user with read access to clients, projects, and employees.
2. Go to **Workspace settings** → **Integrations** → **Deltek Ajera**.
3. Click **Add integration**.
4. Enter your Ajera API URL and the API user.

Only workspace admins can connect or disconnect Ajera.

## Import data

On the integration page, click **Import data**. The stepper runs entities in dependency order, so customers import before the projects and time entries that reference them. It skips entities whose **Read** toggle is off, names them, and links to sync settings.

## What syncs

| Deltek Ajera | Pike | Notes |
| - | - | - |
| Clients | Customers | |
| Projects | Projects | Billing type, budget, and hourly rates |
| Phases | Phases | With budget, under the matching project |
| Employees | Members | Matched by email |
| Timesheet entries | Time entries | With notes and billable flag |
| Invoices | Read-only invoice history | |

### Keep syncing during a transition

**Keep syncing** is off by default. When it is on, Pike imports new Ajera records and time entries every 3 hours, or in real time on the Enterprise plan, so teams can switch over gradually. See [How sync works](https://usepike.com/docs/integrations/how-sync-works.md#migration-integrations).

## Sync settings

While Ajera is connected, the **What syncs with Ajera** card sits under the top button row on the integration page. Each entity has a **Read** toggle (Ajera to Pike). Toggles save immediately.

| Entity | Read | Send |
| - | - | - |
| Clients, projects, and phases | Yes | Not available |
| Timesheet entries | Yes | Not available |

New connections start with **Read** on for everything.

## Synced records

Every synced record shows the Ajera marker, "Last synced {time}" or "Not synced yet", and a **Refresh** action. **Refresh** shows only while **Read** is on for that entity.

### Sync issues

Records that fail to sync appear in the **Sync issues** list on the integration page, with the record, the reason, and a **Retry** action. The integration never deletes Pike data on its own. A record removed in Ajera is marked "Removed in Ajera" in Pike, never deleted.

## Disconnect

Disconnecting Ajera stops syncing and keeps all imported data. Linked records keep their history.

## Permissions

Synced data respects Pike roles and private projects. A private project's tasks never sync out to anyone who cannot see the project in Pike.

## Limits

* Invoices from Ajera import as read-only history.
* Pike does not write to Ajera.

## Related

* [Deltek Ajera integration overview](https://usepike.com/integrations/deltek-ajera): What imports, how teams switch, and FAQs.
* [Deltek WorkBook](https://usepike.com/docs/integrations/deltek-workbook.md): Import customers, jobs, and time.
* [Harvest](https://usepike.com/docs/integrations/harvest.md): Import clients, projects, and time entries.
* [Switch playbook](https://usepike.com/switch): Plan the pilot, migration, and go-live.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.