Talk to us
  • CASE STUDY | SUPPLY CHAIN SUSTAINABILITY / SAAS

Asset data centralized. Manual tracking retired. Automation foundation built.

A global supply chain sustainability SaaS company migrated its hardware asset estate from a legacy tracking system (Asset Tiger) into Jira Service Management Assets, establishing the foundation for automated onboarding and offboarding in a future phase. Trundl completed Phase 1 with 100% data integrity from Discovery to sign-off by early April 2026.

Talk to us
100% data integrity
4+ asset categories migrated
Phase 1 complete, April 2026
Phase 2 automation-ready
  • ON THIS PAGE
Industry Supply Chain Sustainability / SaaS
Region Canada / North America
Solution Asset Tiger to JSM Assets Migration
Timeline Discovery to sign-off, April 2026
Partner Tier Atlassian Platinum Solution Partner
Talk to us
  • THE CLIENT

Who is the client?

A global supply chain sustainability SaaS company serves manufacturers in industrial, medical, and aerospace sectors with regulatory and sustainability solutions. Following rapid growth, the organization’s Atlassian ecosystem had been managed on a best-effort basis, resulting in a disconnected asset tracking system, manual reporting, and no single source of truth for device-to-ticket relationships.

  • THE BUSINESS CHALLENGE

Disconnected assets and manual reporting at scale.

01

Data Silos

Hardware and software assets were tracked in Asset Tiger, separate from the IT service desk, making it impossible to link tickets to specific devices.

02

Manual Overhead

IT staff relied on spreadsheet exports for reporting with no automated view of the asset estate.

03

Infrastructure Gaps

Inconsistent Atlassian configurations and lack of governance slowed team performance and task planning.

04

Scaling Pressure

Rapid company growth required a foundation capable of supporting automated onboarding and offboarding in a future phase.

  • PROJECT OBJECTIVES

Centralized, structured, and automation-ready.

01

Centralization

Consolidate all physical assets (laptops, tablets, and peripherals) into Jira Assets

02

Data Integrity

Standardize schemas to support attribute inheritance across device types, ensuring hardware-specific data flows correctly through parent-child object relationships.

03

Governance

Define administrative and view-only access levels and train IT staff on lifecycle management in the new interface.

04

Phase 2 Foundation

Prepare the environment for future integrations with Okta, Jamf, and Automox.

  • THE TRUNDL SOLUTION

A structured migration from legacy tracking to JSM Assets.

01

Schema Design and Data Transformation

Designed a Jira Assets schema mirroring operational complexity, including attribute inheritance so hardware-specific data (model numbers, warranty dates) flowed correctly through parent-child object relationships.

02

Phased Migration from Asset Tiger

Systematically migrated hardware categories (Laptops, Tablets, Meeting Room devices, and Miscellaneous assets) from Asset Tiger with full data transformation.

03

Differential Synchronization

Performed a final differential import to capture any assets added to the legacy system during the migration window, eliminating the data gap between cutover start and final sign-off.

04

Governance and Training

Mapped administrative versus view-only permissions for the IT team and delivered training on asset creation and lifecycle management in Jira Assets.

  • DELIVERY HIGHLIGHTS

Quality, value, and speed.

QUALITY 100% data integrity

Despite the complexity of manual data transformation across multiple asset categories, every record migrated from Asset Tiger with full fidelity.

TIME TO MARKET Discovery to April 2026

High-velocity delivery from engagement start to production sign-off, positioning the team for Phase 2 automation.

VALUE ADD Automation-ready

The organization is now positioned to automate its full onboarding and offboarding workflow in Phase 2, eliminating the manual IT ticket volume that currently accompanies each hire and departure.

  • FAQ

Frequently asked questions.

Why was the migration split into phases?

Phase 1 stabilized the physical asset data foundation before introducing third-party integrations. Moving to Okta and Jamf before the schema was clean would have produced unreliable automation. Clean data first, automation second.

How was data accuracy maintained during the transition?

A final differential import captured any assets added to Asset Tiger during the migration window, closing the gap between cutover start and final sign-off.

What does Phase 2 include?

Phase 2 is scoped to integrate Okta (people data), Jamf, and Automox, enabling automated device assignment and deprovisioning as part of standard onboarding and offboarding workflows.