When to Migrate a Website (and When Not To)
Migrations have a settling period, so the launch date matters as much as the plan. The months to avoid by industry, the deadlines that force bad timing, and how far ahead of a peak season to land it.
Published August 13, 2026
6 min read
PortMySite
Most migration advice covers how. Far less covers when, which is strange, because the launch date decides how much a mistake costs.
The reason is the settling period. A migration is not finished at cutover. Search engines spend the following weeks re-crawling every redirected address and re-evaluating what it is worth, and during that window your rankings are less stable than usual. Nothing about that is dangerous by itself. It is only dangerous if it coincides with the month you cannot afford a bad week.
The rule that covers most cases
Land a migration immediately after your peak, never before it.
That gives you the full quiet season to settle, and if something does need fixing, you are fixing it while the stakes are low. The instinct to have a beautiful new site ready for the busy season is the one that causes damage, because it puts the least stable four weeks of your site's life directly in front of the traffic that pays for the year.
Your quiet season is not the calendar's
The generic advice says migrate in January. That is right for retail and wrong for plenty of businesses. Work from your own analytics rather than a rule of thumb, and look at the same month across two years before deciding.
- Retail and e-commerce. Move in January or February. Never between October and December, and that includes "just the blog".
- Restaurants. The weeks after the holidays, and away from local events that fill your tables. Avoid the run-up to Valentine's and Mother's Day, which for many kitchens are bigger single days than December.
- Accountants and bookkeepers. Early summer, once filing season is behind you. Migrating in the first quarter is choosing chaos.
- Med spas, salons and aesthetics. After the winter and spring booking rush and before wedding season starts. Late summer tends to be the gap.
- Trades and home services. Deep winter for garden and roofing work; late spring for heating engineers. Whichever end of the year your phone stops.
- Law firms and B2B services. Genuinely flexible, which is a real advantage. August and late December are usually the quietest weeks.
- Anything driven by a single event. Move as soon as the event is over. You have eleven months of margin; use the first of them.
If you cannot identify a quiet season, that itself is useful: it means timing matters less for you and you should optimise for having people available rather than for the calendar.
The deadlines that force bad timing
Most badly timed migrations are not chosen. They are forced, and usually by one of these.
A subscription about to renew. This is the most common, and the least good reason to rush. Renewing for one more cycle costs a fraction of what a compressed migration during a busy month can cost you, and you need the old platform running through the transition anyway. Pay the month.
A price rise. The same logic. A platform raising its price is a good reason to leave and a bad reason to leave this week.
A rebrand or launch date. This one is legitimate, and it means the migration date is fixed. In that case protect the settling period instead: move the site earlier than the brand launch, let it settle quietly on the new stack, then switch the visible branding once the search side is stable. Doing both on the same day means you cannot tell which change moved what.
Something broke. If the current site is down, hacked, or the host has become unusable, timing arguments stop applying. Move now and accept the settling period lands where it lands. A broken site loses more than an unstable one.
Do not launch on a Friday
Search engines do not care what day it is. The people who fix things do.
The first 48 hours after a cutover are when mechanical faults surface: a redirect rule that does not match, a form posting nowhere, a staging setting that shipped. Launching Tuesday or Wednesday morning gives you the rest of the week with everyone available. Launching Friday afternoon means a broken checkout gets discovered by customers over the weekend.
Within the day, pick the quiet hour from your own analytics rather than assuming nights. A restaurant's quiet hour is mid-afternoon. A B2B site's is genuinely overnight.
When not to migrate at all
Sometimes the honest answer is that the timing is a symptom of a bigger problem.
If you are moving because you dislike the design, that is a redesign and it can happen on your current platform for far less. If you are moving because one feature is missing, price the feature before pricing the migration. And if you are three weeks from your peak season with a site that works, the correct move is almost always to wait until January, however much the current platform annoys you between now and then.
We say this to people who are ready to pay us, which should tell you how often the timing is the actual issue.
The short version
Land it after your peak, not before. Give it three months of clear air rather than three weeks. Never launch on a Friday. Renew the subscription you resent rather than compress the work. And if a fixed date is forced on you, protect the settling period by separating the migration from the visible relaunch.
For what happens inside those weeks, the migration timeline breaks the schedule into its phases, and SEO recovery after a migration covers the settling period specifically. If you want a date rather than a range, the quote builder gives you a working delivery date as you answer.
Common questions
- When is the best time to migrate a website?
- Immediately after your peak season, not before it. A migration needs four to eight weeks of settling while search engines re-crawl, so you want that period to land in your quietest months. For most retail that means January or February; for a restaurant it is usually the weeks after the holidays; for an accountant it is the early summer after filing season.
- How long before a busy period should I migrate?
- Three months of clear air, minimum. That covers the build, the settling period, and enough margin to fix anything the settling period exposes. Landing three weeks out is the common mistake: the site is technically live but still re-crawling exactly when the traffic you cannot afford to lose arrives.
- Should I migrate if my platform subscription expires next week?
- Renew for one more cycle and migrate properly. One month of a subscription you resent paying is far cheaper than a rushed cutover during your busiest period, and cancelling the old platform before the new site is verified removes your only rollback. Keep the old subscription running through the transition regardless of when you move.
- Is there a bad day of the week to launch?
- Friday. Not because search engines care, but because the first 48 hours are when mechanical faults surface, and you want people available to fix them. Tuesday or Wednesday morning gives you the rest of the week to catch anything, which is the actual reason experienced teams avoid Friday launches.
- Does migrating during a Google algorithm update matter?
- It mainly makes diagnosis harder. If rankings move during a confirmed update you cannot easily tell which change caused what, and you may spend weeks fixing a migration that was fine. Updates are not announced far enough ahead to plan around, but if one is rolling out in the week you were going to launch, waiting a fortnight costs nothing and keeps the picture clean.
Doing this yourself?
Or hand it to people who do it weekly.
Fixed price, 7-day delivery, full 301 redirect map, no downtime. Send the URL and get a real quote back within one business day.