Joomla Content Migration

  • Joomla Content Migration 1.5 to 3.X

    cms b transparentMigrating Joomla! 1.5 to 3.x is a major migration. Major changes in features and database tables between these two versions makes content migration a pretty challenging task. We take care of this challenging task for you, efficienty and cost effectively.

    We offer:

    Joomla Core data and third-party extension data migration. Joomla Core data (components) are:

    • Categories
    • Articles
    • Menus
    • Modules (core modules - not third-party)
    • Banners
    • Contacts
    • Messaging
    • Newsfeeds
    • Redirect
    • Search
    • Smart Search
    • Weblinks

    Third-party extension migration: needs to be researched to determine if it’s ready for Joomla 3.x and has a migration path or not.

    Services include:

    Prepare a Location for Joomla 3:
    Make sure your server environment meets the technical specifications for Joomla! 3 before proceeding. Note: If your host does not meet the technical requirements, you will need to change hosts.

    Set up a Development Location:
    • Create a testing site or build area to work in with one of the following:
    • A subdomain
    • A subdirectory
    • A local device via WAMP , MAMP , LAMP , XAMPP .
    • A new hosting account on a temporary domain in the root (if you would like to change hosts in the process of migration)
    • Restoring a site on a local device. See Installing Joomla locally and Setting up your workstation for Joomla development.
    • Restoring a site with Akeeba Backup (read the developer documentation or videos for how to restore a backup of an Akeeba Backup file).


    Content Migration Process

    We follow a 26 Point migration process:

    • Migrate all core data you want to move to Joomla 3.x. Move Sections and Categories. 

    • Run the Database Fix

    • Install your new template or converted template so that you can see your content. 

    • Add new menus if the migration tools didn’t bring over menus. 

    • Add modules if the migration tools didn’t bring over modules. Change the module positions to the positions in your new template if required so that your modules show up correctly.

    • Check for duplicate alias issues and fix them.

    • Check internal links. If any are broken, fix them.

    • Take a backup.

    • Install other third-party extensions and configure them (like editors, Akeeba backup, slideshows, or plugins).

    • Take a backup.

    • If your website has large extensions with data to migrate, do each one according to the developer documentation and then take a backup after each one.

    • If our migration tool didn’t move the images, we will move your images from the 1.5 site to the 3.x site. 

    • Fix asset issues. 

    • If you are going to add anything to your site or use new core features like Tags, get them set up and configured at this time.

    • Check your URLs on the Joomla 3 site and compare to the Joomla 1.5 site. 


    • Migration SEO Tips Series - Part 1 - Planning Your Link Migration Strategy ; and

    • Migration SEO Tips Series - Part 2 - Monitoring Your Migrated Site's Health .

    • Take a backup.

    • Check everything.

    • Clean up more.

    • Test everything.

    • Take a backup.

    • Move or change or add updated data from the 1.5 site to the Joomla 3 site.

    • Add google analytics to the template or use a third-party plugin.

    • Check Global Configuration and make sure all is as it should be.

    • Take a final backup of the Joomla 3.x site.

    • Take a final backup of the 1.5 site.

    • Move your 1.5 site from the root to another subdomain or subdirectory or simply delete it (this is so that you have it again for a brief time if you need to refer to it).

    • Backup and restore or simply move files to restore your 3.x site to the root of your hosting.

    • Enable .htaccess if necessary for SEF URLs.

    • Create a sitemap and submit to Google Webmaster Tools or any other search engine you would like.

    • Do all your redirects from the spreadsheet you created earlier for URLs that changed in the migration process.

    • Make any other changes that needed to wait until the 3.x site was live.

    • Test again.

    • Take another backup.

    • Kill any instance(s) of the 1.5 site as soon as possible.

    • Remove all other dev sites you may have been working with or keep them up-to-date if they are running a current version in order to ward off hack attempts on your server.

    • Project delivered!