Integrated Data
Deltek Ajera On-Premise
What this page covers: A complete reference mapping every Deltek Ajera On-Premise field to its Mosaic equivalent. Use this guide when configuring your integration, verifying synced data, or troubleshooting discrepancies.
| Integration type | On-Premise (Direct Database Access) |
| Setup complexity | Moderate — requires SQL Server replication |
| Configurable fields | Limited — most fields have fixed sources |
| Prerequisite | Ajera On-Premise Integration Setup |
How Data Flows
Ajera On-Premise (Direct DB access via SQL replication) → Mosaic Sync Engine (field mapping) → Mosaic (8 synced data types)
The On-Premise integration uses direct database access through SQL Server replication to read data from your Ajera database. Mosaic replicates a subset of Ajera database tables and maps them into Mosaic entities. See SQL Server Integration Requirements for setup instructions.
Integrated Data Types
The integration syncs 8 data categories from Ajera On-Premise into Mosaic:
| # | Data Type | Description |
|---|---|---|
| 1 | Employees | Staff records with names, emails, and titles |
| 2 | Clients | Client records with names |
| 3 | Projects | Project records including descriptions, fees, dates, and billing configuration |
| 4 | Phases | Phase breakdowns under projects |
| 5 | Time Entries | Timesheet transactions with hours, rates, notes, and billability |
| 6 | Rate Groups | Rate table groupings |
| 7 | Roles | Employee roles |
| 8 | Work Categories | Activity categories for time entries |
This list may expand as new features are added. When a new feature is added to Mosaic, you can expect your Customer Success Manager to reach out requesting access to your server to update your replication.
Reading the Field Mapping Tables
Symbol legend for technical tables
The Technical Reference tabs below use a shorthand notation for database sources. Read this legend before reviewing the mappings.
| Symbol | Meaning | Example |
|---|---|---|
. | Database table field reference | AxProject.prjDescription = the prjDescription field from the AxProject table |
→ | Maps to / becomes | AxVEC.vecEmail → Employee Email |
> | Fallback priority — use the first available value | prjActualStartDate > prjEstimatedStartDate = use Actual; if null, use Estimated |
Detailed Field Mappings
Jump to a section: Employees | Clients | Projects | Phases | Time Entries | Rate Groups | Roles | Work Categories
Employees
| What Syncs to Mosaic | Where It Comes From in Ajera |
|---|---|
| Employee Name | The employee's first, middle, and last name |
| Employee Email | The employee's email address |
| Employee Title | The employee's job title |
| Employee Status | The employee's status (active, inactive, etc.) |
| Is Employee Flag | Whether the record is an employee |
| Date Hired | The employee's hire date |
| Description | The employee description |
| Is Client Flag | Whether the record is also a client |
| Last Modified Date | When the employee record was last modified |
Clients
| What Syncs to Mosaic | Where It Comes From in Ajera |
|---|---|
| Client Name | The client name from Ajera |
| Client Title | Mosaic displays client name as "Title" |
Projects
| What Syncs to Mosaic | Where It Comes From in Ajera |
|---|---|
| Project Description | The project description |
| Project Fee | The project fee / contract amount |
| Client | The client linked to the project via Invoice Groups |
| Start Date | The actual start date, falling back to the estimated start date |
| End Date | The actual completion date, falling back to the estimated completion date |
| Project Manager | The employee assigned as project manager |
| Project Status | The project status value |
| Project ID | The project identifier |
| Project Key | The unique project key (primary key) |
| Billing Type | The project billing type |
| Rate Table | The rate table assigned to the project |
| Department / Entity | The project entity |
| Company | The project company |
| Project Type | The project type classification |
| Notes | Notes associated with the project |
| Last Modified Date | When the project record was last modified |
Phases
| What Syncs to Mosaic | Where It Comes From in Ajera |
|---|---|
| Phase Description | The phase description (from AxProject phase levels) |
| Phase Fee | The phase fee / contract amount |
| Start Date | The phase start date (actual, falling back to estimated) |
| End Date | The phase completion date (actual, falling back to estimated) |
| Project Manager | The phase project manager |
Time Entries
| What Syncs to Mosaic | Where It Comes From in Ajera |
|---|---|
| Date | The transaction date of the time entry |
| Hours | The number of units (hours) logged |
| Employee | The employee who logged the time |
| Project | The project the time was logged against |
| Phase | The phase the time was logged against (via project hierarchy) |
| Work Category | The activity associated with the time entry |
| Description | The time entry notes |
| Billable | Derived from the activity type |
| Rate | The cost rate and/or earned rate for the time entry |
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 | The role description from Ajera |
Work Categories
| What Syncs to Mosaic | Where It Comes From in Ajera |
|---|---|
| Activity Title | The activity description |
| Activity Number | The activity key identifier |
Replicated Data Tables
Mosaic replicates a subset of the data tables available in Ajera On-Premise. The following tables are included in your replication:
| Table Name | Key Fields | Usage in Mosaic |
|---|---|---|
| AxActivity | actKey, actDescription, actType | Time Entry integration |
| AxCompany | cmpKey, cmpDescription | Project integration |
| AxEntity | eKey, eDescription, eOverheadPercent | Project integration |
| AxInvoiceGroup | igKey, igClient, igProject | Project/Client integration |
| AxProject | prjKey, prjStatus, prjDescription, prjID, prjProjectManager, prjBillingType, prjRateTable, prjTotalContractAmount, prjActualStartDate, prjEstimatedStartDate, prjActualCompletionDate, prjEstimatedCompletionDate, prjEntity, prjCompany, prjNotes, prjLastModifiedDate, and 30+ additional fields | Project integration |
| AxProjectType | ptKey, ptDescription | Project integration |
| AxTransaction | tKey, tDate, tProject, tEmployee, tActivity, tUnits, tCostRate, tEarnedRate, tEarnedAmount, tBilledUnits, tBilledRate, tBilledAmount, tNotes, tStatus, tIsDeleted, tIsCurrent, and additional fields | Time Entry integration |
| AxVEC | vecKey, vecStatus, vecEmail, vecIsEmployee, vecFirstName, vecMiddleName, vecLastName, vecTitle, vecDateHired, vecDescription, vecIsClient, vecLastModifiedDate | Employee integration |
Cloud vs. On-Prem: Key Differences
Compare Cloud and On-Prem capabilities
The On-Premise version has some differences compared to Cloud:
| Feature | On-Prem | Cloud |
|---|---|---|
| Database access method | Direct database access (SQL replication) | Ajera API |
| Time Entries source | AxTransaction table (direct DB) | AxTimeEntries API (requires Ajera ODBC) |
| Work Categories source | AxActivity table (direct DB) | Requires Ajera ODBC |
| ODBC required? | No | Yes — for Time Entries and Work Categories |
| Full DB table replication | Yes — replicates full DB tables | No — queries API endpoints |
| Access to AxTransaction details | Yes (tKey, tDate, tCostRate, tEarnedRate, tBilledRate, etc.) | No |
| Replicated tables available | Yes (AxActivity, AxCompany, AxEntity, AxInvoiceGroup, AxProject, AxProjectType, AxTransaction, AxVEC) | No |
Troubleshooting & FAQ
How does SQL Server replication work for this integration?
Mosaic replicates a subset of your Ajera database tables to a Mosaic-managed SQL Server instance. For setup requirements, see SQL Server Integration Requirements.
Will my replication tables be updated when Mosaic adds new features?
Yes. When a new feature is added to Mosaic, your Customer Success Manager will reach out requesting access to your server to update your replication.
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 |
Related Documentation
Updated about 1 month ago
