Upgrade Path from Older Versions of Movable Type
Because of various schema improvements throughout the lifetime of Movable Type, the following upgrade path is recommended.
Movable Type 5.x ¶
From the current version of MT you are on, upgrade through each of these key versions of Movable Type to get to MT5.
- MT3.2 - MT-3.32.zip
- MT3.3x - MT-3.38-en.zip
- MT4.x - latest stable version of MT4
- MT5 - latest stable version of MT5
Movable Type 4.x ¶
From the current version of MT you are on, upgrade through each of these key versions of Movable Type to get to MT4.
- MT3.2 - MT-3.32.zip
- MT3.3x - MT-3.38-en.zip
- MT4 - latest stable version of MT4
Tip: Other older versions of Movable Type are available in the Movable Type Archive.
This path is recommended solely based on the fact that Six Apart does not extensively test the upgrade process between versions more than one major version apart. While technically an upgrade from MT2.6 to MT5 or MT4 should work and there are no known issues with upgrading in this fashion, we can only offer upgrade support to users upgrading from one version at a time.
Installation Guides ¶
Movable Type 4 & 5 ¶
- Installation and Upgrade is the same as current Installation and Upgrade docs
Movable Type 3.3 ¶
- MT3.3 Documentation Index
- Important Upgrade Information for MT3.3
- MT3.3 Installation Guide PDF
- A Safe Way to Upgrade to MT 3.3 from Learning Movable Type
- Plugin Compatibility and MT3.3 from Learning Movable Type
Movable Type 3.2 ¶
- MT3.2 Installation and Upgrade
- A Safe Way to Upgrade to MT 3.2 from Learning Movable Type
Movable Type 2.x ¶
Upgrade Tips Specific to Version ¶
Upgrading from MT3.2 or older? ¶
- Rename
mt.cfgfile tomt-config.cgi. - If you're using MySQL or PostgreSQL, move the contents
mt-db-pass.cgitomt-config.cgi.
Upgrading a version older than MT3.31? ¶
Search result feeds script changed location in MT3.31. Add the following code to mt-config.cgi to properly output search results feeds:
AltTemplate feed results_feed.tmpl
This is the default configuration since MT3.3. Doesn't hurt to have this in the config file.
Something Missing? ¶
Please add a comment below.
maddy
January 19, 2010 5:49 PM | Reply
Upgrading from 4.0x with Custom Field plugin to Movable Type Pro?
Upgrading to Movable Type Pro 4.3x (or 5.x) will not automatically migrate custom fields data created using the Custom Fields 2.x plugin created by Arvind Satyanarayan.
If you are upgrading from Movable Type 4.0x and need to migrate existing custom fields and data to the native custom fields implementation provided with Movable Type Pro use the Custom Fields Upgrade Assistant plugin.
Refer to the plugin's README file installation and usage instructions. Due to changes to the implementation of custom fields in Movable Type Pro, do not upgrade directly to the latest Movable Type Pro 4.3x version, instead upgrade to Movable Type Pro 4.13 (available in the Movable Type archive), and then to the latest version.