Shark Software Support @ Links Technology

Who are the customer(s) involved?

Are involved customers Enterprise, Hosted, or VPS customers

What companies are being moved? FERC-registered Name and CIDs.

1. From the source customer:
   1. What TariffShark release is the customer running?
   2. What version of SQL Server are they using?
   3. Is the customer willing/able to send us a database backup? Does personal data need to be redacted?
   4. If necessary, how can we transfer files?
   5. What are we doing with transferred companies' data? Deleting? Updating license to hide data? Updating license to be read-only?
2. From the target customer:
   1. What TariffShark release is the customer running?
   2. What version of SQL Server are they using?
   3. Is the customer willing/able to send us a database backup? If not, can the customer run Import Utility within their environment?
   4. If necessary, how can we transfer files?
   5. Scheduling
      1. When can everyone be out of TariffShark?
      2. We normally budget a day's worth of downtime/quiet period to perform migration

Overview of Steps

Below are the normal steps taken when transferring TariffShark datasets between two companies. Based upon the requirements gathered from the questions above the below steps may deviate depending on the nature of migration.

SC = Source Customer

TC = Target Customer

LT = Links Technology

1. SC ensures TariffShark data freeze
2. SC performs database backup and transfers backup to LT through the agreed-upon file-sharing method
3. SC updates TariffShark license or removes transferred data from their environment
4. SC freeze period ends
5. TC ensures TariffShark data freeze
6. TC performs database backup and transfers backup to LT through the agreed-upon file-sharing method
7. LT downloads and restores backups into the migration environment
8. LT performs data migration
9. LT performs a backup of the new TC dataset and uploads the backup to file sharing portal
10. TC downloads and restores backup into the TC environment
11. TC updates TariffShark license, adding support for transferred companies
12. TC business users verify the new TariffShark dataset
13. TC ends the freeze period
14. Migration Complete

If the Source Customer is unable to provide a full TariffShark backup

When the source customer cannot provide a full TariffShark backup the following steps replace steps 1 – 4 in the normal procedure.

1. LT transfers TariffShark Export utility to SC
2. SC ensures TariffShark data freeze
3. SC creates a blank database on same SQL Server as source TariffShark database
4. SC runs TariffShark Export utility, selecting companies that need to be transferred
5. SC performs database backup of export database and transfers backup to LT through the agreed-upon file-sharing method
6. SC updates TariffShark license or removes transferred data from their environment
7. SC freeze period ends

If the Target Customer is unable to provide a full TariffShark backup

When the target customer cannot provide a full TariffShark backup the following steps replace steps 5 – 12 in the normal procedure.

1. LT downloads and restores backup from SC into the migration environment
2. LT creates the intermediate migration database
3. LT transfers the intermediate migration database, TariffShark Import utility, and any necessary SQL scripts (ex. MapValues.sql) to TC through agreed upon file-sharing method
4. TC downloads and restores backup into the TC environment
5. TC ensures TariffShark data freeze period
6. TC runs TariffShark Import utility procedures
7. TC updates TariffShark license, adding support for transferred companies
8. TC business users verify the new TariffShark dataset
9. TC ends the freeze period
10. Migration Complete

Known Complications

• When both the source and target databases contain any of the following custom fields (TCollationValue, TRCollationValue, TRVCollationValue) special steps must be taken not to create duplicate unique custom fields and ensure that the data using those custom fields is correctly mapped to the existing fields in the target database
• Older versions of the migration tool duplicated the defined Custom Field Types defined in the database. When this is encountered, duplicate Field Types need to be removed and any custom field definition using these duplicate types to be remapped.