Project setup phase for on-premises to on-premises migration

Request the systems for migration from your internal IT department.

• Helix Data Manager server
  A Virtual machine to install the BMC Helix Data Manager server. This server is used to store database migration data exports taken during the migration, so it must have drive space twice the size of your source database.
• Database server
  A Virtual machine with a database server to store a copy of the production database for migration testing and pack refinement. The server must have enough disk space to hold your production data. 
  Important:
  You do not need a BMC Helix setup for this database.
• BMC Helix ITSM upgrade systems
  Development, QA, and, to-be-production systems with an upgraded version of BMC Helix ITSM.  The to-be-production system is your target system. The systems must have enough disk space to hold the data from your existing BMC Helix ITSM system.
• File system
  A reliable and fast file system to which HDM Migration package files can be exported.

Ensure the connectivity between the existing (source) system, all three environments, and the BMC Helix Data Manager system.

Make sure that all the systems in your setup have data connectivity to copy data across the systems with the same network.

Important:

If direct connectivity between BMC Helix Data Manager and the source and target databases is unavailable, follow the migration path for the on-premises to SaaS migration. This requires two instances of BMC Helix Data Manager and the ability to copy files between separate networks.