Arcoro Hub is our solution to help you maintain consistent data across your Arcoro modules by helping eliminate duplicate data entry, minimizing human error, and syncing relevant shared data. Hub works entirely behind the scenes and simply keeps your Arcoro products connected and your data in sync automatically. Beyond keeping your data aligned, enabling Hub is the foundation for a growing set of new Arcoro features and capabilities.
To aid in migrating your organization to Arcoro Hub, we have listed key shared data and fields to audit before you are migrated to Arcoro Hub to minimize any issues. This resource does not currently cover the ExakTime Module organizations. ExakTime will be migrated to Arcoro Hub at a later date.
Table of Contents
What You Need To Do
The only thing that you need to do to prepare for your Hub migration is to audit and correct your data across your Arcoro modules. The actual migration to Hub will be handled by us internally, and we will notify you once Hub is active for your organization.
What May Happen if Auditing is Skipped
Data must match exactly for relevant shared fields across your Arcoro modules, as Hub cannot tell that 'Carpenter' in Core HR and 'Carpenter - Journeyman' in LMS are intended to be the same thing. Failure to audit your data in preparation for your transition to Hub can result in any of the following:
- Duplicate Data across multiple modules.
- Conflicting Values across multiple modules.
- Records Which Should Match, But Do Not
If a value lives in two or more modules today and they do not match exactly, decide which one is correct and clean it up before migration. Post-migration cleanup is significantly more difficult because Hub will have already cascaded the mismatched values to other modules.
What to Expect After Migration
Hub does not change the core experience of your Arcoro products. Your team will still log in and work the same way. The main difference is that certain fields across your Arcoro modules will become view-only once Hub is enabled, as those fields are now managed through Core HR.
Employee data flows between your Arcoro modules automatically and does not require any manual initiation or delays in data syncing. Hub processes updates in the background. Your team will not see a Hub interface or need to take any action inside Hub itself.
There are some key items to be aware of, as they may change how and where you manage data:
- If a work email is updated in one Arcoro module, Hub keeps the other in sync.
- Roles and permissions are managed independently in each product. Hub does not merge or override role settings across any of your products.
-
If you are using Core HR with any other module, Core HR will be considered the source of truth for shared fields amongst your module(s). Any fields that are shared with Core HR will become "Read-Only" fields to help ensure that Core HR is the source of truth amongst your Arcoro modules and limit any potential conflicts. Any field changes or new entities should be created in Core HR so they can flow downstream to other Arcoro modules. You can expand the section below to view what fields will be read-only and what can still be modified in LMS/Performance.
Read-Only and Modifiable Fields in LMS and PerformanceEmployee profile fields that become view-only:
Field Managed By Notes First Name Core HR Last Name Core HR Middle Name Core HR Preferred Name Core HR Job Title Core HR Employee ID Core HR Work Email Core HR Used as the unique identifier across products Work Phone Core HR Mobile Phone Core HR Hire Date Core HR Termination Date Core HR Username Core HR Performance Manager Core HR Location Core HR Updates made in Core HR will automatically sync to Talent. Department Core HR Updates made in Core HR will automatically sync to Talent. Job Code Core HR Updates made in Core HR will automatically sync to Talent. Fields that remain editable in LMS and Performance:
- Groups
- Next Evaluation Date
- Last Promotion Date
- Lock Record Date
- Potential Rating
- Salary
- Ethnicity, Gender
If a value is blank or unassigned in Core HR, LMS, and Performance will display it as "Default". You may see a "Default" entry appear in your Job Code, Department, and Location lists as a result. Changes to these values must be made in Core HR.
- Once Hub is enabled, imports for shared fields must be done through Core HR. The ability to import directly into non-Core HR modules is removed for those fields. You can still import into Core HR as normal.
- Data for the following are not affected or used for Hub and will reside in their respective Arcoro module.
- ATS manages its own candidate and job data. Hub only syncs shared employee profile fields between Core HR and ATS.
- LMS course progress, completions, and certifications are not affected by Hub enablement. Only employee profile fields are impacted.
- Performance review history and completed reviews are not affected. Only employee profile fields are impacted.
- Some fields in Onboarding, such as Hire Date, Pay Rate, and Home Address, are delivered to Hub when an employee completes their onboarding paperwork, not on a regular sync schedule.
What Data You Must Audit
The primary four sets of data that should be reviewed have been listed below. We have also created a checklist, including additional data that should be reviewed.
Work Email in All Modules
Review the "Work Email" field for users across multiple modules as the work email is the key that links the same person's record across all your products. If the same employee has different work emails across products, Hub will not recognize them as the same person, which can cause duplicate or mislinked records.
Job Codes in Core HR and Talent
Job Codes sync bidirectionally between Core HR and your Talent products through Hub. Onboarding and ATS do not sync Job Codes, so no review is needed there.
Pull Job Code lists from Core HR and LMS and/or Performance side by side. Confirm code and description match exactly. Resolve any duplicates or naming mismatches (example: 'Carpenter' vs 'CARP01') before migration.
Departments in Core HR and Talent
Departments sync bidirectionally between Core HR and your Talent products through Hub. Onboarding and ATS do not sync Departments, so no review is needed there.
Compare department lists in Core HR and LMS and/or Performance. Confirm names and abbreviations match exactly. Remove any obsolete or duplicate entries before migration.
Locations in Core HR, ONB, and Talent
Locations sync between Onboarding, Core HR, and your Talent products through Hub. Once Hub is enabled, locations in Onboarding will become read-only and must be managed in Core HR going forward. It is important to reconcile location data before migration so the correct records carry over.ATS does not have employee location records, so no review is needed there.
Compare your location lists across Core HR, Onboarding, and LMS and/or Performance. Confirm names match exactly. Resolve any duplicates or inconsistent naming (example: 'Phoenix Office' vs 'Phoenix, AZ') before migration.
Remove or deactivate any locations that are no longer active so they do not carry over into Hub.
Data Audit Checklist
To help you keep track of what you should check, you can use the checklist below. Keep in mind that the checkboxes will not save your selections between page visits.
| ✓ | Area | For Which Modules | What to Do |
|---|---|---|---|
| Job Codes |
|
Pull/review Job Code lists from Core HR and Talent side-by-side. Confirm code & description match exactly. Resolve duplicates (e.g., “Carpenter” vs “CARP01”). Decide on a single source of truth. | |
| Departments |
|
Compare Departments across Core HR, ET, and Talent. Remove duplicates and obsolete entries. Confirm naming convention (abbreviations vs full names). | |
| Locations |
|
Reconcile Location names across ET, Core HR, ONB, and Talent. If you are using ET, check addresses and latitude/longitude. |
|
| Rate Codes |
|
Review Rate Codes in Core HR. Inactive codes do not delete. Any obsolete codes should be flagged for manual cleanup. |
|
| Employee ID |
|
Confirm Employee ID is consistent for the same person across all modules. Mismatched IDs will create duplicate employee records in Hub. | |
| Work Email |
|
Verify the Work Email is populated and consistent across modules. The work email is used as a secondary identifier; mismatches risk duplicates. | |
| Usernames |
|
Review username conventions across modules. Hub pushes Username outbound only. The desired username format should be determined before your migration. |
|
| Inactive / terminated employees |
|
Decide whether to migrate or exclude inactive records. Confirm Termination Dates are populated in Core HR for the true termination date. |
|
| Multi-business-unit setup |
|
If your organization has more than one business unit, note that outbound Location sync to Onboarding is skipped. |
What & How Data Moves
As there are various fields and entities throughout various Arcoro modules, there are some items that will and will not sync between Arcoro modules, depending on relevance (e.g., while employment type is important for Core HR, it is not relevant for the Talent modules).
Arcoro Module Abbreviations
The following Arcoro modules have been abbreviated for easy reference:
| Abbreviation | Arcoro Module |
|---|---|
| ATS | Applicant Tracking System |
| ONB | Onboarding |
| CoreHR | Core HR |
| Talent | Learning & Performance |
| ET | ExakTime (Time & Attendance) |
Employee Data
Legend
- ✓ - Field present in module.
- ✓¹ - Union sync to/from CoreHR is controlled by "Union" feature of Core HR.
- ▲ - The field arrives after employees and/or managers complete their new hire events, not the regular timer-based Onboarding sync.
- — - The module does not send or receive that field at all.
| Field | Inbound: Module → Hub | Outbound: Hub → Module | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ATS | ONB | CoreHR | Talent | ET | ATS | ONB | CoreHR | Talent | ET | |
| First Name |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
| Last Name |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
| Middle Name |
— |
✓ |
✓ |
✓ |
✓ |
— |
✓ |
✓ |
✓ |
✓ |
| Suffix |
— |
✓ |
✓ |
Baked into Last Name |
✓ |
— |
✓ |
✓ |
Concat. to Last Name |
✓ |
| Preferred Name |
— |
✓ |
✓ |
✓ |
— |
— |
✓ |
✓ |
✓ |
— |
| Job Title |
— |
✓ |
✓ |
✓ |
— |
— |
✓ |
✓ |
✓ |
— |
| Employee ID |
— |
▲ |
✓ |
✓ |
✓ |
— |
— |
✓ |
✓ |
✓ |
| SSN |
— |
▲ |
✓ |
— |
— |
— |
— |
✓ |
— |
— |
| Work Email |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
| Personal Email |
— |
— |
✓ |
— |
— |
— |
— |
✓ |
— |
— |
| Work Phone |
— |
✓ |
✓ |
✓ |
— |
— |
✓ |
✓ |
✓ |
— |
| Mobile Phone |
— |
— |
✓ |
✓ |
✓ |
— |
— |
✓ |
✓ |
✓ |
| Home Phone |
— |
— |
✓ |
✓ |
✓ |
— |
— |
✓ |
✓ |
✓ |
| Home Address |
— |
▲ |
✓ |
— |
✓ |
— |
— |
✓ |
— |
✓ |
| Hire Date |
— |
▲ |
✓ |
✓ |
✓ |
— |
— |
✓ |
✓ |
✓ |
| Termination Date |
— |
— |
✓ |
✓ |
✓ |
— |
— |
✓ |
✓ |
✓ |
| Date of Birth |
— |
▲ |
✓ |
— |
✓ |
— |
— |
✓ |
— |
✓ |
| Gender / Sex |
— |
— |
✓ |
— |
— |
— |
— |
✓ |
— |
— |
| Marital Status |
— |
▲ |
✓ |
— |
— |
— |
— |
✓ |
— |
— |
| Employment Type |
— |
▲ |
✓ |
— |
— |
— |
— |
✓ |
— |
— |
| Pay Rate (Hourly) |
— |
▲ |
✓ |
— |
✓ |
— |
— |
✓ |
— |
✓ |
| Pay Rate (Salary) |
— |
▲ |
✓ |
— |
✓ |
— |
— |
✓ |
— |
✓ |
| Pay Type |
— |
▲ |
✓ |
— |
✓ |
— |
— |
✓ |
— |
✓ |
| Username |
— |
— |
— |
— |
— |
✓ |
✓ |
✓ |
✓ |
— |
| Performance Manager |
— |
▲ |
✓ |
✓ |
— |
— |
— |
✓ |
✓ |
— |
| Location |
— |
▲ |
✓ |
✓ |
✓ |
— |
✓ |
✓ |
✓ |
✓ |
| Department |
— |
— |
✓ |
✓ |
✓ |
— |
— |
✓ |
✓ |
✓ |
| Job Code |
— |
▲ |
✓ |
✓ |
✓ |
— |
— |
✓ |
✓ |
✓ |
| Pay Schedule |
— |
— |
✓ |
— |
✓ |
— |
— |
✓ |
— |
✓ |
| Labor Classes |
— |
— |
✓ |
— |
✓ |
— |
— |
✓ |
— |
✓ |
| Union / Class / Local |
— |
— |
✓ ¹ |
— |
✓ |
— |
— |
✓ ¹ |
— |
✓ |
| ET PIN |
— |
— |
— |
— |
✓ |
— |
— |
— |
— |
✓ |
| ET Security Roles |
— |
— |
— |
— |
✓ |
— |
— |
— |
— |
✓ |
| ET Policy Group |
— |
— |
— |
— |
✓ |
— |
— |
— |
— |
✓ |
| ET Category |
— |
— |
— |
— |
✓ |
— |
— |
— |
— |
✓ |
| ATS Status / Roles |
✓ |
— |
— |
— |
— |
✓ |
— |
— |
— |
— |
| ONB Status / Role |
— |
✓ |
— |
— |
— |
— |
✓ |
— |
— |
— |
| Talent Status |
— |
— |
— |
✓ |
— |
— |
— |
— |
✓ |
— |
| IsLearning / PerfAdmin |
— |
— |
— |
✓ |
— |
— |
— |
— |
— |
— |
Non-Employee Data
This table covers non-employee data (locations, departments, job codes, etc.) and the modules exchange these entities with the Hub.
Legend
- ↔ - Bidirectional Sync
- ⇿ - Conditional Bidirectional Sync
- ⇥ - One Direction Sync
- — - Data does not sync for the module.
| Entity | ET | CoreHR | ONB | ATS | Talent | Notes |
|---|---|---|---|---|---|---|
| Locations | ↔ | ↔ | ↔ | — | ↔ |
Hub → modules: IsOffice=true only. ONB skipped if >1 business unit. ET also syncs IsTimeAndAttendance=true. |
| Departments | ↔ | ↔ | — | — | ↔ | Inactive in Hub → hard deleted in CoreHR and Talent. |
| Job Codes | — | ↔ | — | — | ↔ | Inactive in Hub → hard deleted in CoreHR and Talent. |
| Labor Classes | ↔ | ↔ | — | — | — | CoreHR uses upsert (no deletes); ExakTime syncs the full collection. |
| Pay Schedules | ↔ | ↔ | — | — | — | Inactive in Hub → hard deleted in CoreHR. |
| Rate Codes | — | ↔ | — | — | — | Inactive does not delete from CoreHR. |
| Cost Codes | ↔ | — | — | — | — | TimeStamp type excluded. |
| Jobs (Projects) | ↔ | — | — | — | — | Rich structure: hierarchy, dates, IsCertified, locaion assignments. |
| Unions | ↔ |
↔ (via UDF12–14) |
— | — | — | ExakTime has Union / Class / Local; CoreHR uses custom lookup fields. |
| ATS Roles | — | — | — |
⇥ (ATS to Hub Only) |
— | One-way only; not pushed back to ATS. |
| Location Addresses | ⇿ (Full) | ⇿ (Partial) | ⇿ (Partial) | — | ⇿ (Partial) | ExakTime includes latitude/longitude + address ID; Other modules have address without geo coordinates. |
Where to Audit Data
To help you audit your organization's data, we have provided steps below on where to review the data within the module or generate relevant reports, where available:
Employees & Details (Employee ID, Username, etc.)
Core HR
- Expand Data, expand Export, and click Manage from the menu.
- Hover over Quick Excel Exports in the top menu bar and click Export Employees.
- Review the list and details of the employees in the Excel document.
ATS
- Click Administration from the top menu bar.
- Click User Maintenance from the list on the left-hand side.
- Click Export Users....
- A confirmation dialog will appear to confirm the list of users to export. Click OK.
- Review the user details in the CSV file.
Onboarding
- Click Administration from the top menu bar of Onboarding.
- Click Users.
- Review the list of users in Onboarding.
Talent
- Click Account Admin from the menu near the top-right.
- You should see the People page initially.
- Review the list and details of the users in Talent.
Locations & Details
Core HR
- Expand Setup and click Setup Properties from the menu.
- Hover over Field Value Setup in the top menu bar and click Facilities.
- Review the list and details of the facilities in Core HR.
Onboarding
- Click Administration from the top menu bar of Onboarding.
- Click Locations.
- Review the list of locations in Onboarding.
Talent
- Click Account Admin from the menu near the top-right.
- Click Company Setup to open the menu, click Locations, then click Company Locations.
- Review the list and details of the locations in Talent.
Departments
Core HR
- Expand Setup and click Setup Properties from the menu.
- Hover over Field Value Setup in the top menu bar and click Departments.
- Review the list and details of the Departments in Core HR.
Talent
- Click Account Admin from the menu near the top-right.
- Click Company Setup to open the menu, then click Departments.
- Review the list and details of the Departments in Talent.
Job Codes
Core HR
- Expand Setup and click Setup Properties from the menu.
- Hover over Field Value Setup in the top menu bar and click Job Codes.
- Review the list and details of the Job Codes in Core HR.
Talent
- Click Account Admin from the menu near the top-right.
- Click Company Setup to open the menu and click Job Codes.
- Review the list and details of the job codes in Talent.
Labor Classes
Core HR
- Expand Setup and click Setup Properties from the menu.
- Hover over Field Value Setup in the top menu bar and click Labor Classes.
- Review the list and details of the Labor Classes in Core HR.
Pay Schedules
Core HR
- Expand Setup and click Setup Properties from the menu.
- Hover over Pay Schedule Configuration and click Pay Schedules.
- Review the pay schedules set up for Core HR.
Rate Codes
Core HR
- Expand Setup and click Setup Properties from the menu.
- Hover over Pay Schedule Configuration and click Rate Codes.
- Review the list and details of the Rate Codes in Core HR.
Core HR
- Expand Setup and click Setup Properties from the menu.
- Hover over Field Value Setup in the top menu bar and click the respective User Defined L12, User Defined L13, or User Defined L14.
- Review the list and details of the Unions in Core HR.
ATS Roles
ATS
- Click Administration from the top menu bar.
- Click User Roles from the list on the left-hand side.
- Review the user roles of your ATS.
Locations Addresses
Core HR
- Expand Setup and click Setup Properties from the menu.
- Hover over Field Value Setup in the top menu bar and click Facilities.
- Review the list and details of the facilities in Core HR.
Onboarding
- Click Administration from the top menu bar of Onboarding.
- Click Locations.
- Review the list of locations in Onboarding.
Talent
- Click Account Admin from the menu near the top-right.
- Click Company Setup to open the menu, click Locations, then click Company Locations.
- Review the list and details of the locations in Talent.