Upgrading an old website or online store

Upgrading means replacing the outdated parts of your site with current ones. The aim is that your content, products, orders and page addresses stay as they are, so I check everything in a test copy first. An upgrade can cover:

• the platform itself (WordPress, WooCommerce or OpenCart) to a newer version;
• extensions, plugins and the theme, so they work with the new version;
• the PHP version, the programming language your site runs on at the server;
• the SSL certificate (HTTPS), so browsers stop showing “Not secure”;
• the hosting (the server where your site is kept) – the site can be moved to another provider if your current one no longer fits.

The longer a legacy ecommerce platform goes without an upgrade, the more known security vulnerabilities it carries and the harder the upgrade becomes, because more has to change at once. If the site is already showing errors, those need fixing first: see Fixing website errors.

WordPress and WooCommerce

I update WordPress, its plugins and the theme (the design template). On a WooCommerce shop I then test the cart, checkout, shipping methods and order emails in the test copy. If a plugin is abandoned or does not work with the new version, I tell you what could replace it before changing anything.

OpenCart

After the check, I suggest moving OpenCart 1.5 and 2.x shops to OpenCart 3.0.x, if that suits your shop. I aim to keep the design and the page addresses, so customers and Google find the same pages. The step-by-step process is on the OpenCart upgrade page.

Other systems

If your site runs on another open platform (PrestaShop, Magento, Joomla, Drupal) or custom-built PHP, and I can get access to the admin panel, files and database, I confirm after the check whether I can upgrade it. I do not work on Shopify, Wix or Squarespace sites, because these systems do not provide access to the files.

Past work

• siuvimomanija.lt. An OpenCart shop running since 2010, updated: automatic shipping cost calculation, card payments and SEO (visibility in Google search).
• e.segris.lt. An old OpenCart 1.5 shop: a new look for phones and computers, an SSL certificate (HTTPS), Lithuanian product descriptions with photos and video, SEO.
• A long-term client, UAB “Siuvimo manija”: for two years I have looked after its 6 websites (siuvimomanija.lt, husqvarna-viking.lt, babylock.lt, elna.lt, siuvimomasina.lt and juki.lv).

Screenshots and the e.segris.lt before-and-after comparison are in the Past work section of the home page.

PHP is the programming language WordPress, WooCommerce and OpenCart run on at the server. Hosting providers retire old PHP versions over time. On an old system, that switch can leave you with a blank white page or a PHP error message instead of your shop, or a cart or admin panel that stops working.

I switch the test copy to a newer PHP version and test the platform, theme and extensions. I fix whatever breaks, or upgrade the platform itself. Only when everything works do I change the PHP version on the live site.

Which PHP version an old system can run depends on the system, the theme and the extensions, so I do not promise one in advance; I confirm it after the check.

If you need to move your online store to new hosting or to a different domain, for example because your host no longer supports the PHP version you need or the site is slow, this is how I do it:

1. I make a backup of the whole site and the database;
2. I move the files and the database to the new hosting;
3. I check that the site works in its new place before the domain points to it;
4. I point the domain to the new hosting and check that the SSL certificate (HTTPS) works.

Before the move we discuss email: if your mailboxes run on the same hosting account, they either move with the site or stay with your current provider. The new provider is responsible for its own servers, so I cannot guarantee its service.

1. I review and send a proposal. I review the site and set out in writing what I would do and what it would cost. This is free.
2. I make a backup copy. I copy the whole website and the database, so I can restore everything if needed.
3. I upgrade in a test copy. Every change is tested in a test copy first. Your site keeps running as usual.
4. I move the changes. Once everything is checked, I move them to your live site.

I need access to the admin panel, the website files (FTP or SFTP) and the database, for example through your hosting control panel (DirectAdmin, cPanel or Plesk).

The price is agreed before I start, and you pay in instalments. We can issue a VAT invoice. To keep the system from ageing again, updates can continue under monthly maintenance: see Website maintenance.