website migration launch manager

    2

    Plan and execute safe website migrations with URL mapping, DNS runbooks, and SEO preservation checklists.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    website migration launch manager

    Example session with this skill installed

    Plan a migration from a legacy WordPress blog on 'blog.old.com' to a Subdirectory on a Webflow site 'newsite.com/blog'. We have 500 posts, GA4 tracking, and a launch date of Friday at 8 PM.

    • Read your context and instructions
    • Compiled the website migration launch

    I have developed a migration plan to move 500 posts from your legacy WordPress subdomain to the new Webflow subdirectory. This plan prioritizes SEO preservation and analytics continuity.

    Website Migration Runbook: WordPress to Webflow

    1. URL & Redirect Map (Sample Logic)

    Old Path (blog.old.com)New Path (newsite.com/blog/)Redirect Type
    / (Home)/blog301 (Wildcard)
    /%postname%//post/%postname%301 (Regex)
    /category/%name%/tag/%name%301 (Manual)

    2. Pre-Launch QA Checklist

    • Analytics: Verify GA4 Tag G-XXXXXXXX is present in Webflow Custom Code head.
    • Forms: Update WP Contact Form 7 endpoints to Webflow native forms or Logic flows.
    • Internal Links: Run search-and-replace for hardcoded blog.old.com links in post bodies.
    • Images: Ensure all WP uploads are migrated to Webflow Assets or a CDN.

    3. Launch Day Sequence (Friday 8:00 PM)

    1. DNS Update: Lower TTL on blog.old.com to 300 seconds (Perform 24 hours prior).
    2. Webflow Publish: Deploy to production domain newsite.com.
    3. Redirect Implementation: Apply 301 rules in Webflow Project Settings > Publishing.

    CNAME Record: Update blog CNAME record to point to the new destination or decommission if using platform-level redirects.

    4. Rollback Plan

    • Trigger: Critical form failure or >10% increase in 404 errors in first 30 minutes.
    • Action: Revert DNS CNAME for blog.old.com to the original WP hosting IP.

    Next steps

    • Export your full WordPress XML or CSV list of URLs to finalize the exact mapping.
    • Confirm if the WordPress 'Categories' should map to Webflow 'Collections' or 'Tags'.
    • Audit your GA4 property to ensure the new subdirectory is included in the data stream filter.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Broken redirects and dropped SEO rankings turn website migrations into expensive disasters. This skill prevents launch-day chaos by generating a comprehensive technical migration plan that covers every failure point from DNS TTLs to analytics continuity.

    What it does

    • URL Mapping generates explicit old-to-new path maps to prevent 404 errors.
    • Redirect Strategy defines 301 rules for CMS, hosting, or platform-level implementations.
    • Pre-launch QA builds checklists for content integrity, form functionality, and tracking scripts.
    • Launch Runbook sequences DNS changes and deployment steps with clear ownership.
    • Rollback Planning establishes specific triggers and procedures for reversing a failed deployment.

    How it works

    1. Inventory Collection: Provide your old/new platforms, domain, and specific page groups or URL structures.
    2. Technical Mapping: The agent identifies redirect requirements and tracking dependencies (GTM, GA4, Pixels).
    3. Execution Sequence: You receive a time-blocked launch day runbook and a dedicated post-launch monitoring list.

    Frameworks & tools

    Works with any CMS (WordPress, Shopify, Webflow), hosting provider, or DNS manager. Specific focus on SEO preservation via crawlability checks and analytics continuity.

    Why this beats prompting it yourself

    Generic prompts often miss the "boring" technical details like DNS TTL management or form endpoint verification that actually break sites. This skill enforces a strict sequence that separates verified facts from assumptions, ensuring no one flips a switch without a rollback path.

    Use cases

    • Migrating a legacy WordPress site to a headless Shopify build.
    • Reorganizing site architecture or changing domain names.
    • Transitioning hosting providers while maintaining SEO equity.
    • Moving from a staging environment to a live production server.

    Known limitations

    Does not perform the actual DNS records updates or code deployments. Requires manual input of specific URL lists for high-accuracy mapping.

    Requires manual input of URL lists for mapping. Does not execute DNS changes or server-side deployments directly. Launch actions remain 'planned' until user-verified.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Permissions

    No special permissions declared or detected

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    Plan and execute safe website migrations with URL mapping, DNS runbooks, and SEO preservation checklists.

    This skill uses the open SKILL.md standard. Use it through an MCP-compatible agent connected to Agensi, and check the compatibility information on this page for confirmed agents and required capabilities.

    Connect your AI agent to Agensi through MCP, then ask it to use website migration launch manager on your task. Your agent loads the latest approved version each time. Paid skills require a purchase or active subscription. Skill files are not available for download; your licence does not allow you to save, copy or export any part of a skill.

    New in Business & Operations