To migrate data from MDID2 into MDID3, run the migration tool:
C: cd \mdid\rooibos manage.py mdid2migrate path-to-mdid2-config.xml-file
You must specify the path to the MDID2 config.xml configuration file.
If the file is located on another server, you can copy it to the MDID3 server. If the database connection string in the config.xml file points to localhost or uses a server name that is not accessible to the MDID3 server, change it to something that is accessible to the MDID3 server.
The migration tool may take several hours to run, depending on the amount of data and the speed of the involved servers and network connections.
By default, a log file is created at c:\mdid2-scratch\logs that lists any rows in the MDID2 database that could not be migrated. This may include slides that reference missing images, records owned by users that no longer exist, etc. Usually these errors can be ignored.
The migration tool can be run repeatedly, on the second and subsequent runs it will only migrate changes made to the MDID2 database. This allows it to run fairly quickly, but it also requires a significant amount of system memory.