I find mtwMigrator easy to use and it does a very neat job of moving content and retaining menus. I like the concept and it saves a lot of time pulling data in directly from the 1.0.x site. My modules are missing however (except 4 menu ones) and the documentation is rather sparse.

Note: I could not install version 0.1.1 (or any other version come to that) until I changed my database collation to UTF8 from the default Fantastico collation, using the Phoca tool.

I tried this component after trying the official one but ended up with the same problem. My database of the original Joomla 1.0.12 installation is Latin1/Swedish but the default encoding of the site is UTF-8.

The import garbles all the non-latin characters.

Did not find a solution to this issue yet and so I'm stuck with Joomla 1.0.

A solution to this problem would be appreciated.

Worked perfectly for me!
Great job!

I have had no problem with this extension - (I used the latest version 0.1.1).

It's a little slow and underpowered for moving content (I need to move more than 30,000 items, however. There's NOTHING that's not slow). It also doesn't let you select items to migrate or where to migrate them to (e.g. Move content from Section A, Category B on the old site to Section D, Category E on the new site) - So I would recommend NOT setting up that information on the new site before migration. Migrate first, re-hash it later.

If you're looking for a BULK migration tool...this is it.

Just install it on the NEW site, configure it (e.g point it at the OLD site database/tables - it will move the items into the NEW site tables), and away you go.

It flawlessly migrated my entire user database from Joomla! 1.0 to 1.5. I'm running BOTH versions out of one database, and it moved the data no problem - without corrupting the data on the original site.

Excellent, excellent, excellent!

I tested 3 other converters before trying this one and it just rocks !!

I imported everything from my joomla 1.0 website without a hitch (excepted the images).

Very recommended

I checked the latest stable version 0.0.8 and a beta 0.0.9 and neither one deals properly with the utf8 tables. I'm migrating from utf8 to utf8 and all non latin1 characters come out garbled.

The other thing - the error messages during the installation about the non-existing languages. Why? I do not use those languages nor do I have intention to use them. Should I just install them to avoid the error messages? Those messages should not be there.

I think it is still a work in progress. Too bad. It could have been a very useful tool.

I have a large number of content items I needed to move from an old 1.0.13 site into a new 1.5 site. Being a noob to sql I wasn't looking forward to the migration. Then I found this and my problems were solved. No install issues, intuitive interface, and now I have all that old content in my new site's d'base. If you need to do a similar job, you can'r do without this!

Big thanx to the coders.

I've been needing to migrate some sites for a while....and have just not felt up to it. I took a look at the migration tools... including this one (ver 3, 5 and now 7)...and just felt it wasn't worth migrating.
Today, I had a reason to spend some time with it..and I'm glad I did. Here's my experience, which may help some others with their migration.
I got errors on installation. Language & ini files if I remember. I ignored them (this was a test site), and went to the migrator...then Global Configuration. I put the appropriate hostname/DBname/DBuser/DBpassword that I was migrating from into the appropriate fields. I chose to migrate all tables & Backup.. everything came back ok except the menu items. I got a duplicate key error.
So... I deleted all content, links, categories, sections, menu items (except home..which can't be deleted), users,...everything.... and re ran the migrator.
It migrated everything just fine.
There are some issues with the content, category, section linking... but that's easy enough to fix.
Bottom line... it's better than a poke in the eye with a sharp stick :-)
Thanks for the extension...

Hi, your component is really useful, but I have problem with encoding in migration. My old tables are coded in the same collation as my new Joomla tables (utf8_czech_ci), but after migration a get very messy and unreadable text. After fixing that problem, this component will be VERY useful ;-)

Owner's reply:
Hi skiddy.



Can you send me a mysql dump with these characters that are unreadable?



I need this to test and fix it in a new version.



Take care

What a chore the whole update/upgrade/migration process is! Phew!! And for newbie/novice Joomla "wanna-be's" the patience required can be daunting. As one of the official "wanna-be's" I can say this component is the BEST THERE IS!!

The only problem is language translation - you need a little patience if you need/want a list of a-d rules. The recent update to the software provides wonderful selections for all the content extractions from the database.

Muchas Gracias, mi amigos!!

Una Mujer en Los Estados Unidos - con espanol muy malo!! :)

This unquestionably is one of the best extensions I've purchased.

I used this to migrate a 1.0 site when the official migrator was causing SQL errors. GREAT JOB!

I have had numerous errors trying to use Migrator Tool posted by the Joomla team. Spent way to much time trying to make it work... never did.

This tool was easy to use. Pulled the content, menus, categories and sections over perfectly. No errors. Running on Xampp development server before going live.

NOTE: The meta data (keywords, description) didn't come over, which to the developer (hint hint) should be on the list for the next release.

I was skeptical because I couldn't read the download site (I don't speak Spanish) but because I already had a site running and didn't want to use the 1.0 component migrator, I decided to give it a try.

I was able to take the database from the old site, upload it through Cpanel on the hosting account backup screen, and have that database available to the component.

The install went well into my 1.5 site, and I configured the component with the user on my new (backed up) database.

This "old" database really was old. Mambo old. mos_ prefix old.

The import worked like a CHARM. I was so delighted, this saved me hours of direct database manipulation.

Thank you thank you thank you!

Initially I used this component tool in my home PC test environment. At that time my environment was based on a version of Xampp 1.6.3 which delivered PHP 4.4.7 and PHP 5.2.3. For some reason mtwMigrator just would not work properly for me. It gave me error messages I no longer recall and did not migrate anything. So, I set it aside.

Over the period of the following week I spent at least 24 hours trying to get the main supported migrator to work for me satisfactorily. Nothing seemed to come out the way I wanted it to. Either the regular migrator left things out or did not work at all. Some of the problems were related to errors on my part, but many of them had no explanation at all. It was most frustrating to go through the entire process of generating a new migration script and trying to use it to build a new site based on Joomla 1.5.1 only to receive the most unhelpful message of (to paraphrase here) "your script failed!" This happened to me time after time after time.

Yesterday I upgraded Xampp to version 1.6.6a. That environment provides PHP versions 4.4.8 and 5.2.5. I again tried to use the standard migrator under both versions of PHP. I got the same kind of errors I have been receiving before. On a whim I decided to give mtwMigrator another chance (same version I had used before, 0.0.4). Running under PHP 5.2.5 it worked like a charm! Everything I needed was migrated perfectly.

I really prefer the approach used by mtwMigrator compared to the standard migrator component. The standard migrator component tries to make a replica of your old site reincarnated as a Joomla 1.5.1 site. So, if you have eliminated some standardly supplied modules from your old site (either because you do not use them or, in at least some of my cases, tried eliminating some in the hopes of reducing the workload on the migrator), they won't be in your new 1.5.1 site. Similarly, capabilities you had in your old site, but which are different in 1.5.1, might not be re-created in your new site. For example, in the old site I had a standard core-supplied module called "Syndicate". In Joomla 1.5.1 the standard replacement module is called "Syndication". The use of the standard migrator in building my new site left that capability totally out.

But with mtwMigrator you build a standard 1.5.1 site first, so all of the core-supplied modules are provided. Then the mtwMigrator simply transfers over those users, modules, sections, categories, etc., which are unique to your old site. You can then decide later which of the core capabilities you want to keep, simply un-publish, or eliminate. A much more logical and helpful approach, to my way of thinking.