Migrating from Another System
From Textpattern CMS User Documentation
Blogging and CMS tools fall into one of two categories: They either create static HTML files from the data that's entered and store them on a server for viewing in a browser (for example Blogger). Or they store the data in a database and create the HTML pages dynamically when someone requests to view the page (like b2). Textpattern falls into the second category, in fact all of it's content is stored in a database for retrieval when needed.
Step 1: Mapping Content
The first step in the migration process is to figure out how to get the content from the old system into Textpattern's database and how to do it in a way that's most useful. With the different fields and information that each system uses, sometimes it's hard to map from one tool to another. Luckily most of this is taken care of by Textpattern's Admin > Import code.
We'll talk about each major blogging and CMS system that's available in this appendix. If you're using another product, you may be able to follow the documentation of one that uses the same basic style as your tool. And don't forget to tell about your success in the forum when you get it imported.
The second part of migrating to Textpattern is getting the layout and navigation working. This is very site specific, so we won't talk about many details here. In general, you'll want to convert the existing template to a Textpress "page" and convert existing tags to Textpress tags.
Following are a few guidelines.
Upload all of your images and other media files to your new server. To make things run smoothly, you should keep the same directory structure. For example, this usually means having a /images directory, which would be located in the root of your website where the /textpattern directory is.
By default, Textpattern doesn't use CSS files stored on the server, instead the information is stored in the database using the Styles panel in the admin interface. You don't have to manage your stylesheets with Textpattern, and depending on your use of stylesheets you may not be able to completely (e.g., if you have multiple stylesheets for one page), but your encouraged to use this method if convenient (it makes things easy).
The hardest step is changing the tags to Textpattern. Some systems (like Xoops) uses the concept of "modules" to encapsulate and reuse content. These could be changed to "forms" in Textpattern. Also, if you have any PHP scripting in your page, then you'll want to replace the PHP <? ?> tags with Textpattern's php tag.
Because of the huge differences in templates for all of the different systems, it's impossible to walk you through converting your template to Textpattern. Hopefully these guidelines will help.
Import Scripts in Development
(Add/edit links and start pages as needed.)