Joomla As the Joomla team creates a better and better CMS, lots of us sit with outdated websites that are not supported anymore, or will not be supported in the near future. Developers normally take two routes to solve this. One is to put up a whole new website in a newer version of Joomla and copy and paste articles over, and the other one is to migrate the data. In some cases, the previous articles are simply forgotten, and a new website is started from scratch with no content at all. Since migration looks like such a daunting task, most people avoid it. Migration becomes quite tricky if you have used lots of third party extensions, but if you have a website with 10 000 URL's it's much more viable than copy and paste. This talk will look at how to approach a migration properly, and how to complete it successfully, without hurting current Search Engine Rankings and hardly any downtime. Presenter Paul van Jaarsveld - Kalemanzi Media Solutions (ZA)

1. Migrating Joomla!
Paul van Jaarsveld – @kalemanzi
1

2. Overview
●
Which migration methods
●
Some scenarios
●
Preparation
●
Do it!
2

3. Migration methods
●
1.0 to 1.5 mtwmigrator
●
J2XML (only content and users)
●
Jupgrade – what we will use today for 1.5 to 2.5
●
SP Upgrade – no personal experience
3

4. Scenarios
●
You built the site.
●
You did no build the site.
●
Traffic?
●
Users?
●
How much content
●
Rebuild?
4

5. Be prepared!
●
List all non vanilla extentions
●
Find upgrade / update procedures
●
Start on JED.
●
Look deeper. 1.6, 1.7 usually work for 2.5
●
If upgrade exists, get info together
●
If no upgrade look for alternatives (or hack)
●
Check extentions against security forums
5

6. Be more prepared
●
Non standard folders out of root
●
Look for cron jobs
●
Have a plain text editor to make notes of folders eg
●
Get to know rsync. Makes life easy.
●
Shell access NB. No access, use phpterm.
●
Cpanel and ftp is cool but delayed
●
Make sure there is enough space on server eg. 3X more
6

7. Be even more prepared
●
Have a permissions script handy
●
Make a written plan / check list
●
Have a good host eg. Updated servers etc.
●
Make a backup
●
Have a 2.5 template (mod or new)
●
Make final changes to content in old site
7

8. Rise of the machine
●
Beware of the robots! disallow: /jupgrade/ otherwise new site
gets indexed
Add <meta name="robots" content="noindex"> and
<meta name="googlebot" content="noindex"> to new template
index.php.
8

9. Just do it!
●
Intall jupgrade
●
Fix issues (plugins / javascript errors)
●
Mootools upgrade
●
Change settings
●
Run it
●
Check the new site
9

10. You did it... almost!
●
Install template
●
Check standard modules
●
Install 3rd party stuff
●
Check that URLS are the same
●
Fix components that changed 301 redirect
●
@pe7er's method
10

11. Da beeg switch!
●
Assume it's a busy website
●
Look for any new users / content / sections / cats
●
Move data over (jupgrade parameters)
●
Do final checks to see it's all okay
●
Why I use the switch script and commandline
●
Use rsync to update extra folders
11

12. Closing comments
●
Don't forget to remove the tags you added to the index.php of
your template!
●
This is only one of the ways you can do it.
●
Full CLI migration script would be awesome
●
Php cli?
12

13. Thanks!
●
Questions
●
Comments
●
Suggestions
YOU are JOOMLA!
Background created on Inkscape from a gazillion hexagons by a person who did not leave his credits on OO
E D.
13