--- sourceDocument: Australia Strategic Portfolio Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-business-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Strategic Portfolio Management ft:clusterId : - itbm bundleId : - itbm workflow : - Technology --- # Migration from Test Management 1.0 to Test Management 2.0 # Migration from Test Management 1.0 to Test Management 2.0 {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Migration from Test Management 1.0 to Test Management 2.0 This guide helps ServiceNow customers migrate their test data from Test Management 1.0 to Test Management 2.0, enabling them to leverage enhanced testing capabilities available in the newer version. Migration should first be performed and verified on a non-production instance before executing in production to ensure accuracy and completeness. Show full answer Show less ## Migration Process * **Activate Required Plugins:** Enable the *Test Management 2.0* (com.snc.testmanagement.2.0) and *Test Management 2.0 --- Data Migration* (com.snc.testmigrationv1v2) plugins. * **Migrate Test Data:** Move test suites, test cases, and tests from version 1.0 to 2.0 using the migration tools. Note that test plans cannot be migrated due to significant changes in the data model. * **Verify Migration:** Confirm that migrated data is complete and accurate in a non-production environment before applying the migration in production. * **Convert Test Suites:** Convert test suites and their underlying test cases into test sets and tests in the new system. ## Data Transformation Details * **Test Cases:** In Test Management 1.0, test cases become test versions in 2.0. Key fields such as Short Description and Domain are preserved, and a relationship is created between the test and test set. * **Tests:** Tests from 1.0 convert to test steps in 2.0, maintaining fields like Order, Domain, Detailed Description, Test Data, and Expected Result. Each test step links back to the original test for reference. * **Test Suites:** Test suites become test sets in 2.0, retaining attributes like Name, Owner, and Domain. ## Custom Field Migration If you have custom fields added to Test Management 1.0 tables, you can migrate these fields to Test Management 2.0 by overriding the default field mapping in the script include *TestMigrationTableMapping* . The base mapping is defined in *TestMigrationTableMappingBase*. This allows you to preserve custom data within the new data model. Migrate your test data from Test Management 1.0 to Test Management 2.0, and start using Test Management 2.0 for its enhanced testing capabilities and features. Apply the following migration steps on a non-production instance, verify if the migration is completed as intended, and then perform the migration steps on a production instance. ## Migration steps {#migrate-test__section_migration_steps_overview} To migrate your test data from Test Management 1.0 to Test Management 2.0, complete the following steps in order: 1. Activate the required plugins. For more information, see [Migration from Test Management 1.0 to Test Management 2.0](https://servicenow-prod.fluidtopics.net/QSMMtMtLEEqz7CpPB7zVVQ "Migrate your test data from Test Management 1.0 to Test Management 2.0, and start using Test Management 2.0 for its enhanced testing capabilities and features."). 2. Convert your test suites. For more information, see [Convert test suites](https://servicenow-prod.fluidtopics.net/cmJFrycfFS3xQxu7WJpVVA "Convert test suites in Test Management 1.0 to test sets in Test Management 2.0. Start using Test Management 2.0 for its enhanced testing capabilities and features."). 3. Verify the migrated data on a non-production instance before repeating on production. ## Activate plugins {#migrate-test__section_dyd_l2t_khb} Activate the Test Management 2.0 (com.snc.test_management.2.0) and Test Management 2.0 --- Data Migration (com.snc.test_migration_v1_v2) plugins. ## Migrate data {#migrate-test__section_bjx_m2t_khb} The migration process allows you to move test suites, test cases, and tests. Note: * Test plans cannot be migrated due to significant change of data model. * Test suites, test cases, and tests that are migrated to Test Management 2.0 will not be removed from Test Management 1.0. {#migrate-test__ul_llj_jxb_d3b} Test cases that are migrated to Test Management 2.0 are converted to test versions in the following manner:{#migrate-test__table_bhh_y2t_khb__entry__2} | Test Management 1.0: Test case | Test Management 2.0: Test version | |-|-| | Short Description | Short Description | | Domain | Domain | | Test Suite | Creates a relationship between test and test set | | Prerequisites | Link to the old test case | [ ] {#migrate-test__table_bhh_y2t_khb} Tests that are migrated to Test Management 2.0 are converted to test steps in the following manner:{#migrate-test__table_j2j_fft_khb__entry__2} | Test Management 1.0: Test | Test Management 2.0: Test step | |-|-| | Order | Order | | Domain | Domain | | Detailed description | Link to the old test | | Test | Step | | Test data | Link to the old test | | Expected result | Verification step | [ ] {#migrate-test__table_j2j_fft_khb} Test suites that are migrated to Test Management 2.0 are converted to test sets in the following manner:{#migrate-test__table_qkw_mft_khb__entry__2} | Test set in Test Management 1.0 | Test set in Test Management 2.0 | |-|-| | Name | Name | | Owner | Owner | | Domain | Domain | [ ] {#migrate-test__table_qkw_mft_khb} ## Add custom fields to migration {#migrate-test__section_otd_rft_khb} You have added custom fields to the tables of Test Management 1.0, and want to move the fields to the corresponding custom columns in Test Management 2.0. In such a case, include the custom fields into migration by overriding the mapping information in the script include TestMigrationTableMapping. The default mapping is provided in the script include TestMigrationTableMappingBase. ## Convert test suites {#migrate-test__section_ccc_tft_khb} [Convert test suites](https://servicenow-prod.fluidtopics.net/cmJFrycfFS3xQxu7WJpVVA "Convert test suites in Test Management 1.0 to test sets in Test Management 2.0. Start using Test Management 2.0 for its enhanced testing capabilities and features.") with underlying test cases to test sets and tests.