.dist file, and outputs a migrated
Important points to remember are:
.dist file is not harmed in any way, regardless of the migration outcome.
Migration output always goes to a different location, along with a text
log file that contains execution details..dist files.The following is the log generated while running the migration tool on a very simple
-----------------------------------------------------------------------------–-
C:\Niagara\Niagara-4.1.xx.xx>n4mig C:\niagara\niagara-3.8.111\backups\
backup_Supvsr_150526_1545.dist
INFO [15:48:41 26-May-15 EDT][sys.registry] Up-to-date [92ms]
INFO [15:48:41 26-May-15 EDT][sys.registry] Loaded [32ms]
INFO [15:48:42 26-May-15 EDT][sys] Niagara runtime booted
(" C:\Niagara\Niagara-4.1.xx.xx") on Win-23A9-FCD0-B958-4E02
[15:48:42 26-May-15 EDT][migration]
-----------------------------------------------------------------------------------
[15:48:42 26-May-15 EDT][migration] Migrating station
backup_Supvsr_150526_1545.dist to backup_Supvsr_150526_1545.dist
Station to be migrated: Supvsr
-------------------------------------------------------–---–---–---–---–---–---–--
Migrating station Supvsr to Supvsr
Migration Templates:
1: Controller Migration Template (ControllerMigrationTemplate.ntpl)
2: Supervisor Migration Template (SupervisorMigrationTemplate.ntpl)
You can also use 'c' for default Controller and 's' for default Supervisor template.
Please select a Migration Template: 2
Using Migration Template SupervisorMigrationTemplate.ntpl
Completed Migration
Source: C:\Users\John\Niagara4.0\Rocket Industries\migTemp\Supvsr
Target: C:\Users\John\Niagara4.0\Rocket Industries\stations\Supvsr
Migration Report: C:\Users\jDoe\Niagara4.0\Rocket Industries\stations\Supvsr_miglog
_1505261548.txt
Important Migration Notes - see Migration Report for details
Using Migration Template SupervisorMigrationTemplate.ntpl
config.bog: REMOVED all uses of type niagaraDriver:NiagaraFoxService in bogIn the example above, the migration tool was launched with only the “n4mig” command and the source backup .dist file path, without any options or explicit migration output location. As shown, the migration template was not specified,
so the tool paused and prompted for the migration template (1 or 2). After this was entered, the tool continued processing and completed the migration.
The migration tool posts information while processing the backup .dist file. By default, the migration output goes to the stations folder of your

In this example, notice that the migration process created a Supvsr folder and an associated log file in the stations folder. The target station name is automatically determined from the station name inside the station backup .dist file.
Entries in the log file (migration report) display source and target locations for items written, actions performed, and so on. If needed, you can use command line options to create a greater level of log detail.