Background I'm in the process of converting an ancient Umbraco site to the new version of Umbraco. After attempting to upgrade the existing Umbraco installation, and ending up with a buggy pile of ****, I'm now setting up a brand new system and transferring the relevant content and functions to the new system.
I've managed to import the normal pages by reading the umbraco.config XML and creating pages through the API. But the media section content is another matter, since this it is DB only.
The actual question :-) Will Courier be able to transfer the media content nodes between the two systems, and sort out the conflicting node and property IDs (some media node and property IDs are already used in the target system) while still preserving the correct tree structure?
Courier only supports v4 installations but if the ancient Umbraco site *is* running Umbraco 4 then Courier can move the Media library. You can test it using the free trial from the package repo...
Transferring media nodes between to non-related Umbraco systems
Background
I'm in the process of converting an ancient Umbraco site to the new version of Umbraco. After attempting to upgrade the existing Umbraco installation, and ending up with a buggy pile of ****, I'm now setting up a brand new system and transferring the relevant content and functions to the new system.
I've managed to import the normal pages by reading the umbraco.config XML and creating pages through the API.
But the media section content is another matter, since this it is DB only.
The actual question :-)
Will Courier be able to transfer the media content nodes between the two systems, and sort out the conflicting node and property IDs (some media node and property IDs are already used in the target system) while still preserving the correct tree structure?
Courier only supports v4 installations but if the ancient Umbraco site *is* running Umbraco 4 then Courier can move the Media library. You can test it using the free trial from the package repo...
is working on a reply...