nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Common Data Model Migration

Sam Evans

Hey everyone,

After upgrading to JSM Premium this year, we gained access to Assets! I finally got around to building an end-user hardware CMDB and after several days of work, had it up and running.

Since then, Atlassian seems to have introduced the Common Data Model (CDM), and a new Hardware tab has appeared. I haven’t been able to find a way to migrate my existing setup across.

Would you recommend holding off until a migration option becomes available, or continuing to invest time in my current setup? I’d be interested to hear how others are approaching this.

Accepted answers

Arkadiusz Wroblewski

Hello @Sam Evans

Atlassian said they’re working on a migration tool to help move custom schemas into CDM, including any Jira stuff you’ve got.

For now, it’s a good idea to keep your current CMDB up and running and just play around with CDM using a small CSV import. Both schemas can work alongside each other, so there’s no rush to rebuild everything right away, especially since they’re developing the migration tools. 🙂

https://community.atlassian.com/forums/discussion/comment/3256173#Comment_3256173

Best,

Arek🤠🧙‍♂️

All comments

Narek Pirumyan

Hi @Sam Evans

I’ve had the same question, and during Team Europe I went to their stand and asked it. Their answer was: “That’s actually a very good question”. So actually there is no automated way to do so, and you’ll need to export your data, transform it into the CDM model and import it into CDM.

But if your data is huge and you already have integrations with Jira via custom object fields, it might be worth waiting a bit for a better way of moving.

Regards
Narek

Sam Evans

Thanks @Narek Pirumyan

Sometimes its difficult to know the direction of some of these releases, and whether its worth the config time. It's quite early days for my team with Assets, so might just bite the bullet! I love the UI element of the Hardware tab, and how they present the stock levels etc. otherwise I probably wouldn't bother migrating…

Arkadiusz Wroblewski

Hello @Sam Evans

Atlassian said they’re working on a migration tool to help move custom schemas into CDM, including any Jira stuff you’ve got.

https://community.atlassian.com/forums/discussion/comment/3256173#Comment_3256173

Best,

Arek🤠🧙‍♂️

Sam Evans

Great to know thanks!

Arkadiusz Wroblewski

Nothing to thanks. We are here to help :)

ふましー

To add a source to Arek's answer: in the comments of the Services + Assets announcement, Aditya Mani from Atlassian wrote on 8 July 2026 that they are building a way to move custom schemas to the CDM schemas, including work item links:
https://community.atlassian.com/forums/discussion/3255620/services-assets-one-source-of-truth-with-two-new-purpose-built-schemas

So for a hardware CMDB it is reasonable to keep your current schema running for now and keep notes of any custom attributes you add, so they are easy to map later.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-cloud

jira-service-management

assets

jsm-assets

cdm