I understand that Squiz maintains a migration script for internal use only which it has in the past made available to clients on a strictly no support/no warranty basis. I just wanted to ask if this script is able to migrate assets and contents between two different versions of Matrix; specifically 3.10.2 --> 3.10.0
Or would I have to bring the 3.10.0 up to 3.10.2 first?
Are you talking about extracting some content from one system and inserting it into another?
Hi Avi,
Here's our current set-up:
Machine 1: Matrix (3.10.0) instance 1 & Postgres
----> Site 1
----> Site 2
Machine 2: Matrix (3.10.2) instance 2 & Postgres
----> Site 3
----> Site 4
We are looking to amalgamate these two Matrix instances into one single instance and to have our Matrix on one machine and our DB on the other as follows:
Machine 1: Matrix (3.10.0) instance (upgraded to 3.12.0 post-migration)
----> Site 1
----> Site 2
----> Site 3
----> Site 4
Machine 2: Postgres
Under our current set-up, I want to move the sites on Machine 2 to the Matrix instance on Machine 1 without having to re-create all of the content and links of the migrated sites by hand. They are mainly standard pages, images, internal links etc.
I just want to know if the script is able to migrate our assets and content between two different versions i.e. 3.10.2 --> 3.10.0 in the first instance.
[quote]I just want to know if the script is able to migrate our assets and content between two different versions i.e. 3.10.2 --> 3.10.0 in the first instance.
[right][post=“15023”]<{POST_SNAPBACK}>[/post][/right][/quote]
We have two scripts that combined can probably do most of what you’re looking for, with a little clean-up work afterwards. However, the scripts are designed for v3.12, so you would need to upgrade both systems in order to run them.
Both scripts can be found in SYSTEM_ROOT/scripts/import – you would use export_to_xml.php to export the two existing sites from one instance and then use import_from_xml.php to import those two sites into the other instance. The export script will copy assets, attributes, metadata and permissions, though it may get some things wrong (if for example, the users or schemas don’t exist in the export).
I recommend making a copy of both systems in a test environment, upgrading them and then playing with the scripts. You’ll want to export each site individually so that you can manage the imports better.
These scripts have zero warranty and are not guaranteed to do anything except take up drive space, etc. I cannot stress enough how much testing is required to ensure the import and export are consistent and successful.
Thanks Avi,
Will do.
Cheers…John.