Recommended workflow to merge two NetBox databases?

[MattDRogers]

Here's my situation: There are two remote sites managed by two different teams who never had anything to do with each other. Now the teams will be merged. Each team was keeping its own site documented in its own instance of NetBox. The NetBox data for both sites must now be kept up in one instance of NetBox; a single database.

Can you import an entire Site including all the locations, racks, devices, clusters, VMs and cables? How about the IPAM data? Kind of stuck here. Any insight would be great. Thank you.

[nnerdmann]

I have a Netbox instance and all the data must be regularly synced to another Netbox instance, but with a different tenant. For this use case, I have created a sync script that will connect to both REST APIs and copy the data from one site to another. It is still not 100% stable and you might have to adapt it to your use case, but maybe this is what you are looking for.

https://github.com/nnerdmann/netbox-sync

[MattDRogers]

I'll check it out. Thank you.

[jeremystretch]

There are two remote sites managed by two different teams who never had anything to do with each other.

This is likely going to be your biggest challenge: Adopting the conventions and norms of either team into one. Even if they're using comparable versions of NetBox, each team likely has its own set of device roles, custom fields, and so on that will need to be consolidated.

[MattDRogers]

Yes, we're going to establish baseline conventions for all of that. Change/adopt what makes sense. And make sure we're both on the same (latest) NetBox release. I think since we're both pretty strict about keeping things up-to-date, whoever the responsibility falls to will not be overwhelmed by a bunch of "catching up" at least.