If you’ve been following us over the past week, you’ll be familiar with my top 5 tips for successful migrations; a series of daily tips on how to perform a seamless migration.
In today’s final part, I will explain why you should listen to the migration advice given by your chosen migration team. But first, let’s recap on previous tips.
My first tip kicked off last week with advice on recognising if your migration team can be trusted with your most precious of commodities; your data.
Tip three explained why developers should not be the first choice to perform your migration.
So, what can I tell you to round off this series?
5 – Listen to your migration team and heed their migration advice
You trust your migration team, right? If you read part one, then hopefully you have made a good choice. There are cases where a migration just isn’t viable.
If you are running very old software that is reliant on even older software, then it is not out of the question that a migration is not just difficult but downright impossible.
You might have to bite the bullet and rebuild everything from new rather than migrate what you have. If this is the case, then a good and honest migration team will usually be able to tell you before they sponge away all your budget.
There have been a few occasions where I have had to deliver the bad news myself that no amount of wishful thinking is going to enable a successful migration. In these circumstances your migration team should be able to give you options. Usually you will end up having to pay your developers to build something new.
In this case, the migration team can still help you cut over to the new site and offer advice along the way.
Successful migrations mean doing one things at a time
If you read part two, then you will have seen my key migration advice to not perform development upgrades whilst in the middle of a migration. Obviously, day to day running of the site, e.g. taking orders, updating blogs, adding products, etc., should still be done.
A successful migration may take a couple of weeks, after all, once testing is factored in and it would be foolish in the extreme to stop running your business during that time!
Don’t go performing development upgrades during a migration
What you should not do is change the way your website fundamentally works. Sure, take new orders, just don’t go installing new plugins in Magento or release version 2.6 of your software mid-migration. You will potentially save yourself a small fortune if you listen to this piece of advice outlined in part 3!
Question all migration advice
Finally, a good migration team will have a wealth of experience but, in the event that they offer you migration advice that you don’t like, DO QUESTION IT! There is probably a good reason why the advice was offered and, once you understand that reason, you will feel better about accepting said advice.
Sometimes the migration team will have misinterpreted the situation and the advice may become void. More often than not, however, the migration advice will be sound and proposed to help alleviate risk.
Make sure you are happy with your migration team
The bottom line is that migrations don’t have to be painful. Whichever company you choose for YOUR migration team, and I sincerely hope that it is us, a good migration team should be passionate, experienced, efficient and pragmatic.
Most importantly though, a good migration company will make the whole process painless and leave you in control of your own destiny.
Mikey signing out, connection closed.