Integrated Data

What this page covers: A complete reference mapping every Deltek Ajera Cloud field to its Mosaic equivalent. Use this guide when configuring your integration, verifying synced data, or troubleshooting discrepancies.


Integration type	Cloud (API)
Setup complexity	Moderate
Configurable fields	Limited — most fields have fixed sources
Prerequisite	Ajera Cloud Integration Setup

How Data Flows

Ajera Cloud (API endpoints) → Mosaic Sync Engine (field mapping) → Mosaic (8 synced data types)

The Cloud integration uses the Ajera API to query data from your Ajera Cloud instance. Time Entries and Work Categories require an additional Ajera ODBC connection. See Ajera Cloud with Timesheet Integration for ODBC setup instructions.

Integrated Data Types

The integration syncs 8 data categories from Ajera Cloud into Mosaic:

#	Data Type	Description
1	Employees	Staff records with names, emails, and titles
2	Clients	Client records with names and contact information
3	Projects	Project records including fees, dates, and billing configuration
4	Phases	Phase breakdowns under projects
5	Time Entries	Time entry records with hours, notes, and billability (requires Ajera ODBC)
6	Role Rate Groups	Rate table groupings
7	Roles	Employee roles (derived from employee title)
8	Work Categories	Activity categories for time entries (requires Ajera ODBC)

This list may expand as new features are added.

Reading the Field Mapping Tables

Symbol legend for technical tables

The Technical Reference tabs below use a shorthand notation for API sources. Read this legend before reviewing the mappings.

Symbol	Meaning	Example
`.`	API table field reference	`AxProject.prjDescription` = the prjDescription field from the AxProject table
`→`	Maps to / becomes	`AxClients.clName` → Client Name

Detailed Field Mappings

Employees

What Syncs to Mosaic	Where It Comes From in Ajera
Employee Name	The employee's full name
Employee Email	The employee's email address
Employee Title	The employee's job title
Employee Role	Not available — Ajera Cloud provides Title, Mosaic maps it as Role

Clients

What Syncs to Mosaic	Where It Comes From in Ajera
Client Name	The client display name
Client Key	The unique client identifier (primary key)
Client Status	The client's current status
Client Address	The client's address
Client Phone	The client's phone number
Client Email	The client's email address
Client Title	Not available — Ajera Cloud shows "Name", Mosaic shows "Title"

Projects

What Syncs to Mosaic	Where It Comes From in Ajera
Project Name / Description	The project description
Billable Status	The project billing type — Billable, Overhead Billable, Promotional, Marketing = billable in Mosaic
Budget Status	The project status value (Ajera status to Mosaic status mapping logic applies)
Client	The client linked to the project via Invoice Groups
Project Key	The unique project identifier (primary key)
Fee	The project fee amount
Start Date	The project start date
End Date	The project end date
Project Status	The project status (same source as Budget Status)
Project Manager	The employee assigned as project manager
Department	The project department
Office	The project office
Project Type	The project type classification
Project Category	The project category
Project Group	The project group
Billing Contact	The billing contact for the project
Billing Address	The billing address for the project
Contract Amount	The total contract amount
Contract Type	The contract type
Rate Group	The rate group assigned to the project
Multiplier	The project billing multiplier
Currency	The project currency
Billing Method	The project billing method
Billing Frequency	The billing frequency
Invoice Group	The invoice group
Tax Code	The project tax code
Project Notes	Notes associated with the project

Phases

Link w/ Existing Phase only links the Ajera phase to the Mosaic phase and does not delete or erase data in either system; after linking, Mosaic retains its current values (phase status, number, dates), and on the next Ajera to Mosaic sync those fields update to match the Ajera phase.

What Syncs to Mosaic	Where It Comes From in Ajera
Phase Description	The phase description
Phase Fee	The phase fee amount
Phase Key	The unique phase identifier (primary key)
Phase Status	The phase status value
Phase Start Date	The phase start date
Phase End Date	The phase end date

Time Entries

Requires Ajera ODBC. You can only sync Time Entries from Ajera Cloud to Mosaic with Ajera ODBC. ODBC configuration is optional for general use but required for Time Entries.

What Syncs to Mosaic	Where It Comes From in Ajera
Date	The date of the time entry
Employee	The employee who logged the time
Project	The project the time was logged against
Phase	The phase the time was logged against
Hours	The number of hours logged
Notes	The time entry notes/description
Billable Flag	Whether the time entry is billable

Role Rate Groups

What Syncs to Mosaic	Where It Comes From in Ajera
Rate Group Name	The rate group description from Ajera rate tables

Roles

What Syncs to Mosaic	Where It Comes From in Ajera
Role Name	Derived from employee title — Ajera provides Title, Mosaic maps it as Role

Work Categories

Requires Ajera ODBC. You can only sync Work Categories from Ajera Cloud to Mosaic with Ajera ODBC. ODBC configuration is optional for general use but required for Work Categories.

What Syncs to Mosaic	Where It Comes From in Ajera
Work Category	Activity categories used for time entry classification

Time entry integration configuration may impose additional limitations depending on your Ajera Cloud settings.

Cloud vs. On-Prem: Key Differences

Compare Cloud and On-Prem capabilities

The Cloud version has some differences compared to On-Prem:

Feature	Cloud	On-Prem
Database access method	Ajera API	Direct database access
Time Entries source	`AxTimeEntries` API (requires Ajera ODBC)	`AxTransaction` table (direct DB)
Work Categories source	Requires Ajera ODBC	Direct DB access (AxActivity)
ODBC required?	Yes — for Time Entries and Work Categories	No
Full DB table replication	No — queries API endpoints	Yes — replicates full DB tables
Access to AxTransaction details	No	Yes (tKey, tDate, tCostRate, tEarnedRate, etc.)
Replicated tables available	No	Yes (AxActivity, AxCompany, AxEntity, AxInvoiceGroup, AxProject, AxProjectType, AxTransaction, AxVEC)

Troubleshooting & FAQ

Why do Time Entries and Work Categories require Ajera ODBC?

The Ajera Cloud API does not expose time entry or work category data directly. An ODBC connection is required to access this data. See Ajera Cloud with Timesheet Integration for setup instructions.

What does "Link w/ Existing Phase" do?

It only links the Ajera phase to the Mosaic phase and does not delete or erase data in either system. After linking, Mosaic retains its current values (phase status, number, dates), and on the next Ajera to Mosaic sync those fields update to match the Ajera phase.

I need a data source or field that isn't listed here.

Any integration not listed in this documentation is considered a customization and is charged at an hourly rate. For more information, see Integration Requests.

Deltek Documentation Links

A consolidated reference of all Deltek Ajera documentation referenced in this guide:

Topic	Link
Ajera Online Help	Ajera Help
Deltek Help & Learning	Deltek Help