Connect Ajera
- In Ajera, create an API user with read access to clients, projects, and employees.
- Go to Workspace settings → Integrations → Deltek Ajera.
- Click Add integration.
- Enter your Ajera API URL and the API user.
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
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.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.
New connections start with Read on for everything.
Synced records
Every synced record shows the Ajera marker, “Last synced ” 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: What imports, how teams switch, and FAQs.
- Deltek WorkBook: Import customers, jobs, and time.
- Harvest: Import clients, projects, and time entries.
- Switch playbook: Plan the pilot, migration, and go-live.