OnLink · Buyer's guide
There are five ways to get HR, identity and device data into Jira Service Management (JSM) Assets: a multi-source Marketplace app, one single-source importer per system, Atlassian’s native Data Manager and import types, an iPaaS such as Workato or Zapier, or a custom script on the Assets Imports REST API.
OnLink is a multi-source app: one listing, one license, one price and one security review covering 100+ named HR, ATS, identity, MDM, security, infrastructure and data warehouse sources. Single-source importers start cheaper, but the price climbs with each source and connection you add.
Buzz
Every option below ends with the same thing, objects in an Assets schema. They differ in how many apps you run, who does the upkeep and what you pay as the number of sources grows.
One listing, one license, one security review for HR, identity, device, security and infrastructure sources. OnLink is the example here.
One Marketplace app per system (Pio Intune Importer, Pio Jamf Importer, T4S Intune Connect). Cheap to start, more apps as you grow.
Data Manager adapters, CSV/JSON import, Assets Discovery and the Imports REST API. Data Manager needs JSM Premium or Enterprise; no HRIS adapters.
Workato, Zapier, Boomi, MuleSoft or Tray.ai recipes writing to Assets. Fits teams that already run an integration platform.
Your own scripts on the Assets Imports REST API. No app cost, ongoing engineering time and upkeep.
One price, whatever you connect. OnLink is $575/month for 100 users, and that price doesn’t change as you add sources or connections. Pio starts lower and climbs: its Intune and Okta importers are $100/month each for up to 2 connections, then $500/month each, a 5x jump. Intune, Jamf and Okta together go from $300/month to $1,100/month once Intune and Okta need a third connection.
Beyond Assets imports, OnLink adds four more things in the same app:
Atlassian Government Cloud. OnLink is available on Government Cloud as well as Jira Cloud.
Webhooks. Trigger OnLink’s prebuilt actions from outside systems, alongside Jira Automation rules and workflow post functions.
Teamwork Graph integration. Bring HR, identity and device data into Atlassian Teamwork Graph, not only Assets.
Assets backup and restore. Back up and restore Assets objects at the schema level (Advanced edition).
The main trade-off is breadth per app versus depth per source. Marketplace figures are as listed on Oct 23, 2026.
|
Approach
|
Examples
|
Apps to run for 5 sources
|
What you pay for
|
Best fit
|
|---|---|---|---|---|
|
Multi-source app |
OnLink (Onward): HRIS, ATS, identity, MDM, security, infrastructure, data warehouse |
1 |
One price (Standard or Advanced) for any number of sources and connections |
Several source types, HR + device + identity joined in one schema |
|
Single-source importers |
Pio Microsoft Intune Importer, Pio Jamf Importer, Pio Entra ID and Okta importers, T4S Intune Connect, lovebyte.codes Kandji importer |
5 |
One license per source app; Pio's Intune and Okta importers cost 5x more past 2 connections |
One or two sources needing prebuilt object types |
|
Native Atlassian |
Data Manager adapters, CSV/JSON import, Assets Discovery, Imports REST API |
0 extra apps |
JSM Premium or Enterprise for Data Manager |
Device and security sources with reconciliation; no HRIS adapters |
|
iPaaS |
Workato, Zapier, Boomi, MuleSoft, Tray.ai |
1 platform + 5 recipes |
Platform subscription + build time |
Companies with an integration team and an existing iPaaS |
|
Custom build |
Scripts on the Assets Imports REST API |
0 apps, 5 scripts |
Engineering time and upkeep |
Unusual or in-house sources |
For these 13 common sources, OnLink covers all 13 in one app; Pio needs five apps and covers eight; native Data Manager covers six. Checked against each vendor’s public listings and docs on Oct 23, 2026.
The full OnLink list is on Supported Integration Sources.
|
Source
|
OnLink
|
Pio
|
Data Manager (native)
|
|---|---|---|---|
|
Microsoft Intune |
Yes |
Intune Importer (own app) |
Yes |
|
Jamf Pro |
Yes |
Jamf Importer (own app) |
Yes |
|
Okta |
Yes |
Okta Importer (own app) |
Not listed |
|
Microsoft Entra ID |
Yes |
Entra ID Importer (own app) or MultiSource |
Yes |
|
Iru (Kandji) |
Yes |
MultiSource |
Not listed |
|
CrowdStrike Falcon |
Yes |
MultiSource |
Yes (Falcon) |
|
Microsoft Azure |
Yes |
MultiSource |
Azure Virtual Machine |
|
BambooHR |
Yes |
MultiSource |
Not listed |
|
ServiceNow |
Yes |
No app found |
Yes |
|
Workday |
Yes |
No app found |
Not listed |
|
ADP Workforce Now |
Yes |
No app found |
Not listed |
|
Personio |
Yes |
No app found |
Not listed |
|
NinjaOne |
Yes |
No app found |
Not listed |
OnLink has one price. At 100 users it’s $575/month whether you connect one source or twenty, with no limit on connections. Pio starts low and climbs: you pay for each source app, and its Intune and Okta importers jump from $100 to $500/month the moment you add a third connection. Pio is cheaper while every app stays within 2 connections; past that, OnLink is cheaper and the gap widens with every source.
|
As you grow (100 users)
|
OnLink
|
Pio
|
|---|---|---|
|
Intune, up to 2 connections |
$575/month |
$100/month (1 app) |
|
Add Jamf and Okta, up to 2 connections each |
$575/month |
$500/month (2 apps) |
|
Intune and Okta need a third connection |
$575/month |
$1,100/month (3 apps, 2 on Advanced) |
|
Add Entra ID and BambooHR |
$575/month |
$1,250/month (4 apps) |
|
Add Workday, other HRIS, identity and operation systems |
$575/month |
No Pio app; add an iPaaS or a custom build |
Admin work scales with the number of apps, not the number of sources. For five sources:
Both OnLink and Pio’s Intune and Jamf importers show the Cloud Fortified badge on their listings; check each app’s data access scopes during review.
|
Task
|
One multi-source app
|
One app per source
|
|---|---|---|
|
Marketplace installs and version updates |
1 |
5 |
|
Security and vendor reviews |
1 app's data scopes |
5 apps' data scopes, even from one vendor |
|
Renewals and invoice lines |
1 |
5 |
|
Where field mappings live |
One configuration for all sources |
Separate configuration in each app |
|
Linking people to devices |
Mapped in the same app |
Built across apps with Assets references |
|
Support contacts |
1 vendor |
1 per vendor used |
Pio's Intune Importer. If one system is all you need, a dedicated importer is a simple choice.
Data Manager is included in those plans and reconciles overlapping device records from Intune, Jamf, Entra ID, Falcon, SCCM, Qualys, Tenable and ServiceNow.
If Workato, MuleSoft or Boomi already moves your HR and identity data, adding Assets as one more target may be simpler than a new app.
OnLink runs on Jira Cloud and Atlassian Government Cloud, not Data Center. On Data Center, look at Atlassian's own Assets integrations or a custom import.
Apps such as Asset Management for Jira keep their own inventory; they fit teams that want a separate asset store rather than Assets.
, not only today's. HR, identity and device systems usually arrive together.
A single-source importer or Data Manager.
A multi-source app. Check that every source is on its list.
Keep HR and device data in one app so the mapping lives in one place.
Add Assets as a target there.
With the table above, including sources and connections planned for next year.
Price OnLink at your user tier on the Marketplace, or book a 30-minute call and we will map your sources with you.
No. OnLink has one price based on your Jira user count: $575/month at 100 users on Standard, for any number of sources and connections. Advanced, which adds Assets backup and restore, is $600/month.
Yes. OnLink imports Microsoft Intune and Jamf Pro (plus Iru, Workspace ONE and others) in one app. Pio sells separate Intune and Jamf importers. Data Manager supports both on JSM Premium and Enterprise.
It depends on how many connections you need. At 100 users, OnLink is $575/month with no limit on connections. Pio’s three importers total $300/month while Intune and Okta stay within 2 connections each; once both need a third connection, the total jumps to $1,100/month. Data Manager covers Intune and Jamf but doesn’t list Okta.
For one source, Pio’s individual app is a good start. For several sources, or any HR system, OnLink covers them in one app; Pio has no Workday, ADP or Personio importer as of October 2026. On price, OnLink is one price: $575/month at 100 users for any number of connections. Pio starts at $100/month per app and jumps to $500/month per app past 2 connections, so two Pio apps past 2 connections cost $1,000/month.
In Pio’s importers, a connection is one link from the source system to JSM Assets, with its own destination and schedule. Standard allows 2 per app, for example 2 Intune-to-Assets connections; more needs Advanced. OnLink doesn’t limit connections.
Yes, with a Marketplace app or an iPaaS. Data Manager doesn’t list HR adapters. OnLink supports 20 HR and payroll systems, including all three.
Yes, when HR and device data both land in Assets with a shared key such as email. A multi-source app maps both in one place.
OnLink is available on Government Cloud. For other apps, check the hosting options on each Marketplace listing.
Yes. OnLink’s Advanced edition backs up and restores Assets objects at the schema level.
Yes. OnLink imports Microsoft Intune, Jamf Pro and Okta (plus Entra ID, Iru, Workspace ONE and 100+ other sources) from one app at one price. See the full list of sources OnLink connects to JSM Assets.
One app, one price
OnLink is $575/month at 100 users for any number of sources and connections. Cloud Fortified, 5/5 from 21 reviews.
List the HR, identity and device systems you will want in Assets over the next 12 months, then price each option at your user tier. The full OnLink source list and the Supported Integration Sources page are the quickest way to check coverage.
What you get with one multi-source app:
