Data Migration Best Practices

Data migration from Fiber Manager 10.x to Fiber Manager XI can target the Asset Package, file geodatabase, or enterprise geodatabase in the customer’s XI data model. See the Configuration topics in this guide for optional points in the implementation where data migration can take place.

Before starting migration, note these key concepts and preparation steps:

• The Fiber Manager XI data model was created as a “UN upgrade” of the Fiber Manager 10.x sample model, not a complete replacement of it.

• At the spatial or feature level, all 10.x feature classes move into one of two XI feature classes. See Feature Class Mapping and Data Model Changes for more information.

  • Patch locations, splice points, slack loops, and other junction features move to the Communications Junction feature class.

  • Fiber cables move to the Communications Line feature class.

• Update the port and strand tables with the toplevelcmn and toplevelguid attributes. See the Fiber Objects topic for more information.

• At the non-spatial level, the tables are mostly unchanged. Migration at this level consists of copying data from the 10.x database to the XI database. See Object Class Mapping for more information.

• The XI database continues to use related objects as the 10.x database does. UN non-spatial objects are not used.

• When migrating data between databases, use copy and paste tools instead of export and import tools. This action prevents the assignment of new Global IDs to migrated asset records.

• When using ArcGIS geoprocessing tools, always choose the “Preserve GlobalIDs” option to prevent assignment of new Global IDs to migrated asset records.

• For most projects, data migration can be accomplished with the Append tool. The Append tool supports basic field mapping between datasets. This best practice topic assumes you are using the Append tool.

• For larger and more complex projects, data migration can involve a variety of custom fields across 10.x feature classes. In this case, consider using the following geoprocessing tools in the Utility Data Management Support toolbox.

  • CreateSimpleDataMapping - creates a spreadsheet you can use to map your current geodatabase schema to the schema of an asset package for a utility network.

  • CreateMigrationWorkspace - creates a data model and data loading workspace suitable for data loading.

  • CopyFieldsAndDomainsFromMapping - copies fields and domains from FeatureClass/Table to FeatureClass/Table defined in the mapping worksheet.

  These tools enable more advanced field mapping based on a mapping spreadsheet. This best practice topic assumes you are not using the Utility Data Management Support toolbox.