Best approach for migrating branch-versioned Utility Network data from UN v5 to UN v7 with schema changes?

[KAUSHIKDAS]

Hi All,

I am looking for advice on the best approach and recommended tooling to migrate data between two separate Enterprise Geodatabases (EGDBs) running different versions of the ArcGIS Utility Network.

Our Current Setup & Goal:

• Source: Utility Network Version 5 (running on branch versioned data, published as a Feature Service).

• Target: Utility Network Version 7 (also branch versioned and published as a Feature Service).

• Schema Difference: The target UN v7 contains added Asset Groups and Asset Types that do not exist in the source v5 schema.

• Goal: Migrate/copy the existing data from the source UN feature classes to the corresponding target UN feature classes, while mapping the new classification and preserving critical identifiers like Global IDs (to maintain association/relationship integrity).

Questions for the community:

1. What would be the recommended workflow?
2. What would be the best tools for the job?

I would highly appreciate any architectural guidance, step-by-step workflows, or lessons learned from anyone who has navigated a similar migration!

[gis_KIWI4]

@KAUSHIKDAS - Since you are already working with a Utility Network you could use the "Transfer Utility Network Data" within UDMS. This tool should maintain all the relationship classes and GlobalIDs.
The tool can take data from the AP and transfer that to an UN or  an AP. 

Just to be safe, I would test this out on UN in mobilegdb. 

Export UN_v5 to AP with data. 
Export UN_v7 to AP to a mobilegdb.
Use tool to transfer data to mobileGDB. 
Test
If that works then use the tool on the eGDB.

The question remaining is the changing of attributes from features in v5 going into v7. 
You can do that post migration before re-enabling topology assuming all AssetTypes and AssetGroups from v5 exist in v7.