Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Splitting WHD between organisations

Hi, we currently use WHD and our organisation is about to de-merge and become two separate entities. Both would like to continue to use WHD and take their respective tickets, assets, history, etc. with them. Thinking about the best way to go about this. In terms of licensing we are splitting the licensing so that's not an issue.

Do we create another WHD instance and import all the tickets, then in each WHD instance we delete the other tickets, assets, clients, etc. for the other? My only thinking then is we'd be left with a lot of gaps in ticket numbers, asset numbers, etc. but I guess that isn't the end of the world, moving forward they'd be sequential.

Has anyone else done this or can offer a better way of going about it?

Thanks in advance,

Ben.

Find more posts tagged with

Accepted answers

All comments

justin.gray

We were able to share the same instance. It does take a fair bit of planning and tweaking of Tech Permissions, Tech Groups, etc.

It was a toss up between the effort involved in deploying an additional system plus managing, patching, upgrading, backing up two separate systems, versus tweaking the existing instance to meet the requirements of two different departments. However, it seems to be working well so far.