Security and technical support for Joomla 1.5 has ended in September 2012. It does not mean that your website will stop working. Only that your website will now be susceptible for hacking or being compromised.
Joomla is not providing any security patches for Joomla 1.5.
Extensions for Joomla 1.5 are not supported any more. Thus, if hackers find vulnerabilities with an extension, they can compromise your website.
Since the extensions for Joomla 1.5 are not being supported, it means that they are not improved. Some extensions might even stop working.
Web hosting providers are upgrading PHP, an essential part for Joomla web hosting to PHP 5.4 or 5.5. Your Joomla website might stop work or bring up lots errors one day.
There have been instances where web hosting providers have shut down Joomla 1.5 websites.
Since your website is an essential part of your business, you do not want your clients or visitors see a hacked website or a website that throws up hundreds of errors. It can result in lost revenue.
Visit the following links for more information:
Joomla 3.5 is mobile-friendly. Thus, you will not be required to design a separate mobile website.
Search engine optimisation (SEO) improvements.
One-click updates of extensions and Joomla.
New features such as Redirect, Smarter Search, built-in Captcha, multi-language support.
You get the latest security patches and bug fixes.
The best extensions supports the latest version of Joomla.
Joomla 3.5 uses the latest technologies such as HTML5.
The following are the recommended settings for Joomla 3.5: PHP 5.4 +, MySQL 5.1 +, Apache 2.x +
No core files of Joomla should have been changed.
The free space must be at least 1.5x of the used space. Thus, if you have used 300MB of your space for example, then you should have 450MB of free space.
The client must provide the Control Panel and FTP login details. Otherwise, the migration will be delayed.
The hosting package must provide for an additional database.
Back up the website.
Download the backup and duplicate the backup on the localhost to ensure that it is working.
Update Joomla 1.5 to the latest version which is Joomla 1.5.26.
Undertake a website audit.
Delete unused extensions and clean the trash.
Check whether there are equivalent Joomla 3.5 versions for the extensions. Some extensions are free, others will have to be purchased
If there are, check whether any data migration is required.
If there isn't, check for equivalent extensions.
Install migration component.
Enable Mootools Upgrade plugin.
Start or restart the migration process.
It is important to note the following about the migration:
Sometimes the website does not migrate on the first attempt. Thus, there might be a few attempts.
That most modules, components, plugins are not migrated and have to be re-installed and configured afterwards, that is, if there is a version for that particular extension
The migrated website will have the default Joomla template and will not look anywhere like your website. Only the default Joomla templates are migrated.
The content such as Sections, Categories, Articles, menus, custom modules will be migrated.
A subfolder called: jupgrade is created with the migrated website. The migration does not make any changes to the files of your existing website whatsoever. Your Joomla 1.5 website will be intact.
Install the modified template or new Joomla 3.5 mobile-friendly template.
Tweak the template, if need be.
Reposition the core Joomla modules.
Re-install and configure the modules, components and plugins or install and configure their equivalents. This is where most of the hard work is.
Re-organise the Categories.
Verify that all external and internal links are correct
Forms will have to be re-created, for example
The client will be provided with the opportunity to double-check that they are satisfied with migration to the extent that their website looks, feel and work like the Joomla 1.5 website.
Any changes suggested will be effected within the scope of the migration.
There will be additional cost if the client wants FLOSSNet to make changes to the website. This will be communicated beforehand.
Client signs off on the migration.
The original website is backed up and relocated to a subfolder
The migrated website is backed up and the folders and files are copied to the root folder.
It is preferable that the new website is moved over on a weekend, to ensure that any hitches are attended to.
In order to quote accurately for a migration, we need to audit the extensions that are installed. In so doing, we will have a sense of what the cost implications would be. However, since people do not know us, they will be loathe to provide us with login details. In so doing, we can only provide an estimate of what we see on the website. Thus, we might not be aware of all the extensions installed when providing an estimate for the migration of the website. If it is minor then we incorporate it in the migration, if it is significant, then we will let you know.
Now, if you are considering to make use of the FLOSSNet migration service, then we advise you to download and then upload the Forum Post Assistant file which can be found at the following website address:
http://forum.joomla.org/viewtopic.php?f=714&t=793531 under the heading Download.
You will find instructions of the website. What it does, is to provide an overview of the website in terms of installed extensions, the version of Joomla, PHP, MySQL, etc. This will enable us to provide a more accurate quote. If you wish, then we can upload for you.
An upgrade is when you move your website from say Joomla 2.5.19 to Joomla 2.5.22.
A migration is not a revamp of the website.
The Backend of Joomla 3.5 looks different from the Joomla 1.5 Backend. Thus, you will require some time for familiarisation.
The migration steps are iterative, since one might have to restart the process from scratch.
A migration is moving your website from Joomla 1.5 to Joomla 3.5. The migrated website will have the same look and feel of the original website if the same template is being used. It should also work like the Joomla 1.5 website.
The website should not be updated once the migration has started, unless the client is content to update the information again on the migrated website.
If there are things not working on the Joomla 1.5 website, it will also not work on the migrated website. However, there will be an additional cost if the client wants it to be fixed on the migrated website.
In some instances the migrated website will not look exactly like the Joomla 1.5 website due to the fact that the modules, plugins and components used on the Joomla 1.5 website might not be available for Joomla 3.5 or if there is a Joomla 3.5 version, it might not have the same features.