> _Q. Why stick with an old content management system?_
> A. Because trying to move the data to a new one is far, far too difficult. (Or expensive. Or complicated. Or, in an absolute worst case scenario involving really horrific hosting situations, impossible.)
In the last year, I’ve had several clients ask me to move them away from Movable Type to the CMS(Content Management System) of their choice.
### Movable Type to Textpattern
Textpattern has an import utility that offers the choice of using either the native MT(Movable Type) export flatfile or the MT database information for a straight database-to-database conversion. In my experience, it munges categories and “forgets” to include entry basenames on the database import, causing organization and display problems. These problems can be solved by using phpMyAdmin to restore categories across the `textpattern` table and a small PHP script to run through the entries adding the `base_url` field.
### Movable Type to WordPress
The import utility for WordPress reads the entire MT export flatfile into a string and proceeds to use array operations to break it up. With a large data set, the server runs into issues with memory or script timeouts and breaks down after importing a portion of the file. This import process requires breaking up a large flatfile into smaller chunks to allow the import script to handle it.
### Movable Type to Joomla!
Joomla! has no built-in comments facility, so it is necessary to install MosCom to handle comments that are imported from MT. Joomla! uses some MySQL reserved words as column names, complicating SQL statements by requiring the prepending of table names. MosCom uses `varchar()` to store comment date and time as strings in separate columns instead of the more commonly used @datetime@. This conversion requires a custom import script to move data from the MT database to the Joomla! database.