Migrating from Legacy WordPress to Custom Next.js

[ Phase 1: Days 1–7 ]
Automated WP REST API Ingestion ──▶ Clean Markdown / Headless JSON Data Layer
        │
[ Phase 2: Days 8–18 ]
Component Architecture ──▶ Next.js 15 App Router + Tailwind CSS Design System
        │
[ Phase 3: Days 19–24 ]
Edge Redirect Mapping ──▶ Comprehensive 1:1 301 Redirect Rules at Cloudflare / Vercel Edge
        │
[ Phase 4: Days 25–30 ]
Staging Verification & Automated Cutover ──▶ Zero SEO Drop & Instant measured Load

// middleware.ts
import { NextResponse } from 'next/server';
import type { NextRequest } from 'next/request';

// Hashmap of legacy WordPress permalinks to clean Next.js paths
const REDIRECT_MAP = new Map<string, string>([
  ['/services/custom-software-development-company-india/', '/services/custom-software'],
  ['/category/tech-insights/core-web-vitals/', '/blogs/core-web-vitals-mobile-optimization-india'],
  ['/contact-us-mumbai-office/', '/#contact'],
]);

export function middleware(request: NextRequest) {
  const pathname = request.nextUrl.pathname;

  // Normalize trailing slashes
  const cleanPath = pathname.endsWith('/') && pathname.length > 1 
    ? pathname.slice(0, -1) 
    : pathname;

  if (REDIRECT_MAP.has(pathname) || REDIRECT_MAP.has(cleanPath)) {
    const destination = REDIRECT_MAP.get(pathname) || REDIRECT_MAP.get(cleanPath);
    return NextResponse.redirect(new URL(destination!, request.url), 301);
  }

  return NextResponse.next();
}

export const config = {
  matcher: ['/((?!_next/static|_next/image|favicon.ico).*)'],
};