Our Website Migration Went Horribly Wrong. Here’s the Checklist We Wish We Had.

At IT Training & Consulting, Inc. (ITTC), we know a thing or two about technology. In fact, our entire business in Los Angeles revolves around helping other companies navigate the complex world of IT, from managed services and cloud consulting to network infrastructure and cybersecurity solutions. We pride ourselves on being the experts, the ones who prevent disasters before they happen.

But even experts make mistakes. And last year, when we decided to migrate our own website to better serve our clients, we learned that lesson the hard way. We didn’t just have a few hiccups; we had a full-blown, teeth-gritting, traffic-cratering nightmare. We failed, and it cost us.

We are sharing this story not to embarrass ourselves, but because we don’t want other businesses in the Los Angeles area to make the same mistakes. The migration was a humbling experience, but it taught us exactly what to do. This is the checklist we wish we’d had on Day One.

The Los Angeles Reality Check: Why Your Website Matters Here

Los Angeles is a unique business environment. It’s a sprawling city of immense opportunity, but it’s also fiercely competitive. Whether you’re a film production house in Hollywood, a logistics company near the Port of LA, a healthcare provider in the Valley, or a tech startup in Santa Monica, your digital presence is your storefront. It is often the first, and sometimes the only, impression you make on a potential client.

Here in California, consumers and businesses are digitally savvy. They expect speed, security, and a seamless user experience. A slow or poorly designed website doesn’t just annoy people; it actively drives them to a competitor. “Good IT support isn’t just fixing issues, it’s anticipating them,” says Abner Navarro, Network Support Specialist at ITTC. “A website migration failure is a prime example of an anticipated disaster that too many businesses walk right into.”

We failed to anticipate. We assumed our technical expertise in other areas would carry us through. We were wrong. A 2025 report from Ahrefs found that a staggering 60% of website migrations result in a measurable loss of organic traffic. A separate analysis of nearly 900 migrations cited by Search Engine Journal showed that the average time to recover pre-migration traffic is a soul-crushing 523 days. For a Los Angeles business, that’s over a year of lost leads, lost sales, and lost momentum. That is a risk no one can afford.

Phase 1: Planning for the Move (And Not the Disneyland Kind)

Benchmarking Your Digital Footprint

The most critical phase of a migration happens before any code is written or any content is moved. It’s the planning phase, and it’s where we made our first major mistake. We were so focused on the “new and shiny” that we didn’t take the time to truly understand what we had to lose.

The starting point for any successful migration is a comprehensive audit. You must create a “before” snapshot of your current website. This isn’t optional; it’s your only point of comparison after you launch.

• Run a Full Site Crawl: Use a tool like Screaming Frog SEO Spider. Run a complete crawl of your current live site and export all the data. You need to archive:

  • Every single URL.

  • The HTTP status codes (identifying existing 404s, 301s, etc.).

  • Title tags, meta descriptions, and heading (H1, H2) structures.

  • Canonical tags and indexation status.

• Audit Your Performance and Traffic: This is not just about looking at your homepage traffic. You need to get granular.

  • Google Analytics (GA4): Export data on your top organic landing pages by traffic and conversion rate.

  • Google Search Console (GSC): Download your top-performing pages by clicks and impressions. Identify the pages that rank on the first page of Google for your most valuable keywords. These pages are the engines of your business.

This benchmarking is the foundation of your whole project. Without it, you are flying blind.

The 3-Tier Priority Matrix for Your Content

Not all pages are created equal. A blog post from 2018 that gets five views a month is not the same as your primary Managed Network Services page or yourIT Support Services in LA page, which are driving a constant stream of high-quality leads.

For us, this was a key insight we wish we had acted on sooner. Before you start moving anything, you need to create a priority list for your pages.

• Tier 1: High Ranking & High Traffic: These are your golden geese. They are the pages that consistently bring in the most organic sessions and conversions. These require a flawless, one-to-one URL preservation or 301 redirect. No exceptions.

• Tier 2: High Authority: These pages might not get tons of traffic, but they have a lot of external backlinks from reputable sites. They carry “link equity” that boosts your entire domain’s authority. This “link juice” must be preserved via 301 redirects.

• Tier 3: Strategic: These are pages that support your marketing campaigns or are integral to your site structure for customer journeys.

Lesson learned: For every single high-value page, we should have identified a specific, relevant destination on the new site’s architecture. We did this for a few pages but assumed we could figure out the rest later.

Choosing Your Team and Timing

A website migration is a complex project that requires the collaboration of multiple departments. You need system admins, developers, content writers, SEO specialists, and designers to all be on the same page . At ITTC, we had our Full Stack Developer Abbas Arif and Software Engineer Juan Alvarez working diligently on the build, but we could have done a better job looping in other team members earlier in the process to prepare for the content migration.

Furthermore, never, ever launch on a Friday. We did, and it was a disaster . If something breaks on a Saturday morning—and something always needs attention in the first 24-48 hours—your team is scrambling to fix it on a weekend when response times are slower and people are harder to reach. We spent a Saturday manually troubleshooting database issues because an integration didn’t reconnect properly after the move.

• Launch on a Tuesday or Wednesday, giving you a full working week to catch and stabilize issues before the weekend .

• Choose a quiet time of year for your business. For most e-commerce brands, this is Q1 or early Q2. Avoid launching right before your peak season, as this can devastate your revenue .

Phase 2: URL Strategy and Redirection Planning

The Art and Science of the 301 Redirect

This is the single most important technical aspect of any migration. A URL is an online address. When you move to a new building, you don’t just abandon your old one and hope people find you. You put a sign on the old building telling people where the new one is. That sign is a 301 redirect.

A 301 is a permanent redirect. It tells search engines that a page has moved permanently and that all the SEO value (link equity) from the old page should be transferred to the new page. We treated our redirects as an afterthought, and it cost us dearly .

• Build a Redirect Map: Create a spreadsheet with every single old URL and the exact new URL it should point to .

• The One-to-One Rule: For Tier 1 and many Tier 2 pages, the redirect must be one-to-one. Do not redirect a high-value old service page to your new homepage. This is the equivalent of sending someone to your corporate headquarters when they were looking for a specific store. Google expects to see thematically relevant content. If you redirect everything to the homepage, Google may treat these as “soft 404s” and you will lose your rankings .

• Avoid Redirect Chains: A redirect chain is when /old-page-1 points to /new-page-1, which then has its own redirect to /new-page-2. This slows things down for users and search engines. Keep it direct .

• Implement at the Server Level: Server-level redirects (.htaccess, Nginx config) are faster and more reliable than client-side redirects (JavaScript or meta refresh) .

Lesson learned: We created a simple 301 redirect map for our primary services, but we failed to map hundreds of other pages, including old blog posts, media files, and campaign landing pages. This created a massive number of 404 errors (page not found) for both users and Google.

Phase 3: The Technical Launch Day Checklist

Launch day is not a time to relax. It is a technical audit marathon. Our nerves were shot after weeks of stress, so we let our guard down. Big mistake.

A Critical Pre-Launch Step: The Staging Environment

A staging environment is a copy of your new website that is hidden from the public and search engines. This is where you should be doing all your testing. We built our new site on a staging server, which was a smart move. However, our fatal error came when we failed to properly configure it.

• Block Search Engines: You absolutely must put a password on your staging environment or use a disallow: / rule in your robots.txt file . If you don’t, Google will try to crawl and index your unfinished, half-broken staging site.

• Remove Staging Blocks at Launch: When you’re ready to go live, you must immediately and carefully remove these blocks. We forgot. When we went live, we left a noindex tag on the new site.

The Technical Pre-Flight Check

This is the checklist we completely fumbled. Use it to avoid our pain.

• Remove Indexation Controls: The moment the new site goes live, verify that the Disallow: rule in the robots.txt and all noindex meta tags have been removed from the production environment .

• Redirect QA: Use a crawler (like Screaming Frog) to crawl your old URLs list and confirm that every single one returns a direct 301 status code to the correct new URL. We did this manually for a few pages, but we missed dozens of broken redirects .

• Core Site Health Check: Spot-check the live site . Visit the homepage, your highest-priority service pages (like your Corporate Cloud Computing page), and your contact page. Make sure they load correctly and aren’t returning errors.

• Sitemap Submission: Generate a new, clean XML sitemap that lists only your indexable URLs and submit it in Google Search Console .

• Change of Address (If Applicable) : If you’ve changed the domain name or a subdomain, submit a Change of Address request in Google Search Console. We failed to do this for our main blog, which caused immense confusion for Google .

Phase 4: The Post-Mortem and Recovery (What We Actually Did)

The first week after our disastrous migration was a blur. The calls from clients complaining about broken links, the panicked looks from our CEO, Juan Turcios, as he watched our organic traffic graph plummet. It was our worst nightmare.

After we’d steadied the ship by fixing the immediate issues, we began the long, arduous process of recovery. We had to go back to basics and perform our own post-mortem.

48-Hour and 7-Day Post-Launch Crawls

We ran a full site crawl of the new, live website and compared it to the “before” snapshot we had taken (thankfully, we had at least done that). The results were sobering .

• New 404 Errors: Dozens of internal pages were broken.

• Missing Metadata: We found pages that had no title tags or meta descriptions.

• Non-Preferred URLs: Some pages were being indexed with weird parameters, creating duplicate content.

Monitoring and Recovery: The Long Game

We learned that a temporary decline in traffic and rankings for a few days or a week is normal. What you need to watch for is a sustained decline.

• Daily GSC Monitoring: We monitored the Coverage Report in Google Search Console daily. We looked for any sudden spikes in “Excluded” or “Error” pages .

• Traffic Analysis: In Google Analytics, we tracked our key landing pages to see if they were recovering. It took months for our top blog post—a cornerstone piece about “Outsourcing Your IT”—to regain its position on the first page of Google.

• Conversion Tracking: We confirmed that our forms, phone tracking, and lead generation pathways were working. We discovered our contact form was broken for three days, costing us who knows how many potential clients .

This entire process taught us a painful lesson: a website is not just a brochure. It’s a complex, living part of your business infrastructure. It’s as important as your network, your servers, and your phone system. And it requires the same level of planning, expertise, and foresight.

Our Proactive Checklist for You

The nightmare we went through is avoidable. If you’re a Los Angeles business owner considering a website redesign or migration, don’t learn the hard way like we did. Here is the checklist we wish we had from the very start.

The Ultimate Website Migration Checklist

1. Plan & Audit (The “Before” Phase)

   • Crawl your entire old website with Screaming Frog.

   • Back up all content, media, and databases.

   • Audit your highest-value pages using the 3-Tier Priority Matrix.

   • Set your launch date for a Tuesday and during a quiet business season.

2. The Redirect Mapping (The “Heart” of the Migration)

   • Create a master spreadsheet mapping every single old URL to its new destination.

   • Ensure a 301 (permanent) redirect is planned for each old URL.

   • Avoid mass-redirecting to the homepage.

3. Staging & Pre-Launch Testing

   • Block the staging site from search engines using password protection or a robots.txt file.

   • Test your new site on staging to catch issues in a safe environment.

   • Run a technical SEO audit on the staging site to catch duplicate titles, broken links, etc.

4. Launch Day

   • Remove staging blocks: Kill the password and robots.txt Disallow rule the moment you launch.

   • Implement and test redirects: Use a crawler to confirm all 301s are working perfectly.

   • Submit your new XML sitemap to Google Search Console.

   • Use the Change of Address tool in GSC if you’ve changed your domain.

5. Post-Launch Monitoring & Recovery

   • Monitor Google Search Console daily for errors.

   • Run a full site crawl 24-48 hours after launch to find and fix any issues.

   • Track your keyword rankings and organic traffic meticulously.

   • Be prepared for a 2-8 week recovery window and have patience.

A professional web migration is not just about coding and design; it’s about preserving the digital equity and reputation you have worked so hard to build. At ITTC, we understand this better than anyone. We’ve turned our painful experience into a refined process for our clients, incorporating it into our comprehensive Web Design Services and broader IT Strategy & Planning.

We don’t just build websites. We architect a resilient and profitable digital presence for your Los Angeles business. Ready to talk about your next project?

Ready to Make Your Next Website Move the Right Way?

If you’re a Los Angeles business owner who has been burned by a bad migration or is looking to redesign your website without losing traffic, we can help. Call the experts at IT Training & Consulting, Inc. today.

Contact us at (844) 804-4882 or fill out our contact form, and let’s build a digital strategy that works for you.