As part of an organizational move to a new, consolidated Active Directory domain, we're taking the opportunity to replace our aging Notification Servers with new, properly spec'ed out systems. Currently a 1 by 2 hierarchy in one of the old domains. All systems are Client Management Suite 7.5 SP1 HF4. Original servers are Windows 2008 R2, new servers are Server 2012 R2 Standard. At the moment, the new servers are set up with brand new CMDBs in a clean, fresh 1x3 hierarchy (we're adding another region) in the target domain. One bonus: SQL servers hosting the CMDBs, both old and new, are already in the new domain.
Ideally, we'd love to carefully, selectively migrate things over to the new system, leaving behind a few accumulated years of "cruft". However, I've spent the last week or so experimenting with the various import\export tools Symantec provides (Connector, the Migration Wizard, the importexport command line utility, Chevron, etc) and I'm finding we almost have too many different options for going about this, with potentially the simplest being just moving to the new servers and retaining the existing databases.
I realize starting clean probably entails a lot more work, but our system has been updated clear through the "7's" (7.1 vanilla through every hotfix up to current) so I could certainly see the advantage of new DBs. Just not sure if that's biting off more than we can chew.
So because I sometimes just can't make a recommendation without knowing every option, I figured I'd poll the Connect community. What would you do and why would you go that route?
Possible factors: domain trust in place between the domains, about two dozen custom inventory data classes and a half dozen custom asset classes. Anything else you'd need to know to throw in your two cents, feel free to ask.