mt2publ 0.1.1
A tool to convert a Movable Type site to a Publ site
Requires Python: >=3.4
Keywords: blog conversion movabletype mt publ

# mt2publ

A tool to (partially) convert a Movable Type website for use with Publ.

## Basic usage

Currently only SQLite databases are supported (although adding direct support for MySQL and Postgres isn't too hard). If you have a MySQL database dump you can convert it to SQLite via [mysql2sqlite](https://github.com/dumblob/mysql2sqlite), and for Postgres you can follow [these instructions](https://manuelvanrijn.nl/blog/2012/01/18/convert-postgresql-to-sqlite/).

```
pip install mt2publ
mt2publ -b BLOG_ID -c /path/to/site/content database.db
```

If you don't specify `-b` then it will dump all entries and category metadata from the MT database, which is probably not what you want if you have multiple blogs configured on the dashboard. You can find the specific blog ID by looking at its URL from the dashboard.

## Current status

It has been tested successfully to extract entries and categories from a single Movable Type 4.21 website.

## Features

### What's supported

* Markdown, Rich Text, and HTML entries (both with and without "convert linebreaks" set), with both intro and extended text
* Publication status:
    * "Draft" and "Scheduled" supported directly
    * "Review" becomes "HIDDEN"
    * "Spam" becomes "GONE"
    * "Published" tries to do the right thing with Publ's scheduling model
* Category metadata
* Blog metadata (stored on the root category)
* Multiple categories with some limitations:
    * It tries to infer the actual category based on the entry's primary category and what other subcategories an entry is in
    * All category placements are set in metadata headers, allowing manual cleanup (and fancy template logic if you so choose)
* Sets path aliases of "entry" and "page" assets based on the original template mappings
* Preserves the original entry ID as `Import-ID`
* `Entry-Type` for entry vs. page
* `Atom-Tag` for the original, inferior atom `<id>` elements

### What won't be supported

* Asset relocation
* Converting HTML/richtext entries to Markdown (use [Pandoc](http://pandoc.org) if you're feeling brave)
* Native multiple categories (unless those become [supported by Publ](https://github.com/PlaidWeb/Publ/issues/163))
* Things which are absolutely too complicated to get right, such as:
    * Full automated template conversion

### What's feasible

* Limited template conversion as a starting point
* Limited category path alias support
* Native support for MySQL, Oracle, and Postgres databases
* Tags
* Output backends for other blogging systems (Jekyll, Pelican, etc.)
* Comment export (probably using the WordPress comment dump format, since many hosted comment systems support that, notably Disqus)

## Data compatibility notes

### Entry dates

The `Date` and `Last-Modified` are based on local time, since Movable Type only provides a single global timezone offset (not even a locale!) for the *entire blog*.

### Feed `<id>`s

`Atom-Tag` potentially leaks data and shouldn't be used, unless you are really worried about Atom feed subscribers seeing duplicate entries. If you still want to use this feature, the appropriate XML fragment would be:

```jinja
{% if entry['Atom-Tag'] %}
<id>{{entry['Atom-Tag']}}</id>
{% else %}
<id>urn:uuid:{{entry.uuid}}</id>
{% endif %}
```