Best Practice Approach for migrating custom tables, forms and fields to a green-field instance

This article provides a high-level overview of the steps required to migrate custom tables, forms and fields to a green-field instance.

1. Migrate any custom roles using Precision Bridge.
2. Identify all custom tables that will need to be migrated.
3. Identify all OOTB tables that have had custom fields (prefixed u_) added to them. The Precision Bridge difference report can be used for this purpose by comparing the customised table on the source instance with the same OOTB table on the target.
4. Use Precision Bridge to migrate all custom table definitions using the Precision Bridge Table Migration template. It will require the output from (2) to configure the migration.
5. Use Precision Bridge to migrate the form and UI for all custom tables using the Precision Bridge Table Migration - Forms and UI template.  This will require the output from (2) to configure the migration.
6. Use Precision Bridge to migrate the custom fields that have been added to OOTB tables using the Precision Bridge Table Migration template.  This will require the output from (3) to configure the migration.
7. For the tables identified in (3) Delete all the existing forms (sys_ui_form) on the target. These will need to be re-created to mirror those on the source sever using Precision Bridge.
8. Use Precision Bridge to migrate the forms and UI for the tables identified in (3) using the Precision Bridge Table Migration Forms and UI template.
9. There may be a need to use other templates/ projects to migrate custom business rules/scripts etc. Best practice is to only migrate missing system objects, not to update any that already exist.

   Other best practice advice on instance migration to greenfield

   To avoid complexity in references to users and groups, use Precision Bridge to migrate these instead of relying on an interface such as LDAP. This will ensure that the sys_id’s remain the same and simplify later migration of data.

   Similarly for CMDB, use the Precision Bridge Form Mapping Wizard to migrate this rather than discovery or templates.

   Avoid manually recreating any foundation/config data. Either use Precision Bridge to migrate this, or update sets. This will again ensure that the sys_id’s remain the same.

   Migrate all configuration/foundation data before migrating ticket data.

Migrate all configuration/foundation data before migrating ticket data