Why change a source?
Organizations change sources when:
Migrating to a new HRIS platform
Switching from a file-based feed to an API-based HRIS (or vice versa)
Replacing a test or sandbox HRIS connection with production
In most cases, you reconfigure the existing source inside the same project rather than deleting the project or creating a new one from scratch.
Why this does not break integrations
Integrations read from a project's standardized fields, not directly from your HRIS:
HRIS (source) → Project (standardized fields) → Integrations → Vendors
When you change the source, you update what feeds the project—but integrations keep reading the same standardized field names (for example, first_name, employee_id, salary). As long as you remap the new HRIS columns to those same standardized fields, downstream integrations continue working without reconfiguration.
Before you change the source
Document current mapping — Note which HRIS columns map to which standardized fields, or download project configuration if available.
Obtain new HRIS credentials — API keys, client ID/secret, SFTP details, or vendor-issued credentials for the new system.
Plan standardized field parity — List standardized fields your integrations depend on and confirm the new HRIS can supply equivalent data.
Coordinate timing — Schedule the cutover when integrations can tolerate a brief data refresh window.
Change the source (recommended workflow)
1. Open the project source
Log in to your Aragorn AI account.
Open Data Projects and select the project.
Click the existing source you want to change.
2. Update connection to the new HRIS
Open Source settings (settings icon in the source configuration area).
Update connection settings for the new HRIS—for example, change the first_name, base_URL, company_ID, or credentials.
Save the connection.
If your UI requires selecting a different platform type entirely, you may need to create a new source in the same project and retire the old one—see When to delete the old source.
3. Remap to the same standardized fields
Open source mapping on the project.
Map columns from the new HRIS to the same standardized fields your integrations already use.
Use Fetch latest fields if the new HRIS exposes columns not yet visible.
Save mapping.
Goal: The standardized field interface stays consistent—even though the underlying HRIS columns may have different names.
Old HRIS column | Standardized field | New HRIS column |
|
|
|
|
|
|
4. Sync data from the new HRIS
Run Sync new updates to pull data from the new HRIS connection.
Review Sync history for success or errors.
Inspect the final dataset—confirm record counts and key field values look correct.
Use Reprocess last sync only if you changed Aragorn configuration (mapping, filters) but the HRIS data itself has not changed. For a source migration, you typically need Sync new updates to import from the new system.
See How to sync a source.
5. Verify integrations
Open connected Integrations and review eligibility record counts.
Run integrations in test mode to confirm output looks correct.
Check integration job history for validation or mapping errors.
If standardized fields were removed or renamed, update integration mappings before enabling live sends.
Reconfigure vs create a new source
Approach | When to use |
Reconfigure existing source | Replacing HRIS on the same primary data project; keeping the same standardized field interface |
Add a new source | Running old and new HRIS in parallel during a transition period |
Delete old source, add new | UI does not allow changing platform type on the existing source connection |
In most HRIS migrations, reconfigure the existing source is preferred—it preserves project history and minimizes integration impact.
When to delete the old source
Delete the old source only when:
You added a new source to the project and no longer need the previous connection
The old source was a temporary sandbox or test connection
Before deleting, confirm integrations receive data from the new source. See How to delete a source.
Warning: Deleting a source stops HRIS imports from that connection. Do not delete until the new source is syncing successfully.
Common issues after changing a source
Issue | What to check |
Integration record count dropped | Eligibility criteria, mapping gaps, or missing standardized fields |
Sync failures | New HRIS credentials, permissions, or API access |
Wrong field values in integrations | Source mapping—new HRIS column mapped to wrong standardized field |
Missing fields | Use Fetch latest fields and bring in new fields |