First thing we want to make sure is that all the content your developers have been working on is checked in and that no one is making any changes to it during the migration process.
You can force the content to be checked in, however your content developers will lose any changes they have made. To avoid upsetting a lot of people, you’d probably be better off just reaching out to users and having them check in EPAKs they’ve been working on.
Click here for more information about determining how to verify whether content is checked out and by whom.
However, if you need to force all the content to be checked in you can do so by highlighting all items in the library (that are currently checked out) and then selecting Override Check Out from the Administration menu at the top.
Confirm you want to discard any changes made to the content by the author.
Next, select Details View in the EPAK Developer client and select all content, with the exception of the System folder.
Then click on Tools, and select Export and Documents.
Specify the destination for your data to be exported to in a form of an .odarc file and click on the Export button.
Once completed successfully, you’ll want to copy the resulting .odarc file to the server you are migrating the content to.
On the new EPAK server start the EPAK Developer Client. We’ll now need to click on Tools and navigate to Import then select Documents.
Click on the Browse button, and specify the location of the .odarc file you have copied over from the old EPAK server.
By default Import Content to box will be populated with /Import. If you want the content to be available in the Library root just specify / instead. Then click on the Import button.
Lastly, we want to check in all the documents to make them available to end users. Right click on the Library root, and click on Check In.