This page will provide general advice and a step by step guide that describes how to migrate a district from SSDT Classic Software to SSDT Redesign.     

General Advice

• Preliminary Migration Testing

  • It is recommended that you start test importing the district's data two months before dual processing begins.  ITCs should execute test imports in a near production environment.   It is important to review the import log files to ensure successful Classic data migration.

  • District staff should be encouraged to use the applications after these test imports are completed.  This will help verify accurate migration of the data and also allow the personnel to gain familiarity with the interface.

  • If possible, third-party applications used by the district should be tested using these preliminary instances.  Check the list of Known Third-Party Vendors to determine the SSDT's last known integration status for specific vendors.  A sample letter is available on the bottom of that page, which can be used to contact the vendor if they are not listed. 

    • If you do contact a vendor not listed or have a status update for one of the listed vendors please contact the SSDT so this wiki page can be updated.

• Historical Transactions

  • The SSDT recommends that all of the district's live Classic data be migrated including up to 10 years of history.

    • Loading more than 10 years of history is possible.  However, retaining the additional data has diminishing value and Redesign may not always be able to accurately reflect very old Classic transactions.

• Average Extract and Import Run Times

  • Based on our experience a district with an ADM of 1800 and 7 years of Classic data will take about 7 minutes to extract from Classic and roughly 2 hours to import into Redesign.

  • This is a baseline measurement and there are many factors that can increase or decrease this run time, but should give you a general idea of the time frames required.

  • District size, the amount of historical data retained in the live files and available system resources will be the primary factors that affect the extract and import processing times.

Step-by-step guide

1. Install Docker

2. Set up nginx-proxy or other reverse proxy to provide secure application access

3. For Each District

   1. Configure the docker instance on the server, see Setting up a District Instance

      1. New to Docker?  Here are some Useful Docker Commands

      2. Make sure you review the JVM Configuration for suggested container memory settings

   2. Migrating Data from Classic

      1. Migrate Data From Classic USAS into USAS-R

      2. Migrate Data From Classic USPS into USPS-R

      3. Migrate Data from Classic EIS into Inventory

   3. Not Migrating from Classic?  Please review New District Setup for details on starting a brand new district on Redesign.  

   4. At this point you'll want to ensure the district's third party vendors work with the Redesign.  

Contact SSDT for assistance

ITC personnel can create a service desk ticket using one of the methods below.  End users should direct questions to their ITC first.  The ITC can escalate these questions to the SSDT as needed.

• Preferred method:  SSDT Service Desk Portal

• Email questions to ssdt-support@nwoca.org

Troubleshooting errors

• If you need to send files to the SSDT for assistance in diagnosing the problem, please see Securely Send Files to SSDT for Support

• Useful troubleshooting links
  
  

  • Diagnosing a Hung Application

  • Using System Monitor Metrics

Related articles