[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-355413-105":53,"doc-detail-355413-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","website-migration-runbook-protect-the-traffic-you-already-have","Website Migration Runbook - Protect the traffic you already have","","A structured website migration runbook that protects existing traffic by planning the rollback before cutover, sequencing migration steps, and assigning named ownership with clear rollback triggers. It emphasizes building a crawl-based URL map, capturing baseline metrics and inventory prior to changes, validating redirects and canonical tags, and performing bulk testing rather than sampling. The guide covers staging verification, DNS and email readiness, cutover execution, rollback design, and post-migration monitoring to prevent irreversible losses.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/website-migration-runbook-protect-the-traffic-you-already-have/355413/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/website-migration-runbook-protect-the-traffic-you-already-have/355413.png","ImageObject",442,249,{"name":88,"@type":89},"Maya Linwood","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-29","2026-09-22",true,{"@type":98,"interactionType":99,"userInteractionCount":15},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the biggest predictor of a clean migration?","Question",{"text":108,"@type":109},"Whether the URL map was built from a crawl or from someone’s memory of the site.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"Why should baseline numbers be captured before migration?",{"text":113,"@type":109},"A migration cannot be proven successful without metrics from before the cutover, and those values are impossible to reconstruct afterward.",{"name":115,"@type":106,"acceptedAnswer":116},"What does the runbook recommend for redirects validation?",{"text":117,"@type":109},"Test redirects in bulk using an automated checker against staging, instead of relying on spot checks or sampling.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},355413,1791718668,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":15,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":79},962084928432,"https://ap-avatar.wpscdn.com/davatar_155a257f0dc6eb9ab79c44ca47cae57d","Gatilab FREE TEMPLATE  \nDELIVERY TEMPLATE  \nWebsite Migration Runbook  \nA migration plan that protects the traffic you already have, with the rollback written before the cutover rather than during it.  \nMigrations lose traffic for boringly consistent reasons: an incomplete URL map, canonical tags pointing at the old host, or a cutover nobody could reverse. This runbook sequences the work, keeps a real inventory, and forces a rollback decision with a named owner and a trigger before anything moves.  \nWHAT ' S INSIDE  \n01 How to use this runbook  \n02 Migration types and what each risks  \n03 Inventory and baseline  \n04 The URL map  \n05 Pre-cutover build  \n06 Cutover sequence  \n07 Rollback plan  \n08 Post-migration monitoring  \nSTART HERE  \nHow to use this runbook  \nThe single biggest predictor of a clean migration is whether the URL map was built from a crawl or from someone's memory of the site.  \n1 Baseline first. You cannot prove a migration went well without numbers from before it. Capture them in section 3 and keep them.  \n2 Crawl the old site, do not list it. Sites always contain more indexed URLs than anyone thinks, and the forgotten ones are usually the ones with links.  \n3 Change one thing at a time. A redesign, a platform change, and a domain change in one release makes any traffic drop impossible to diagnose.  \n4 Write the rollback before the cutover. Under pressure, nobody designs a good rollback. Decide the trigger and the owner while it is still hypothetical.  \n5 Expect a dip and say so up front. A short fluctuation is normal. Setting that expectation before launch is the difference between a routine week and a crisis call.  \nSITE MIGRATION TYPE PLANNED CUTOVER  \nSECTION 1  \nMigration types and what each risks  \n\n| TYPE | WHAT CHANGES | MAIN RISK | TRAFFIC RISK |\n| --- | --- | --- | --- |\n| Hosting move | Server only | DNS and email cutover, missed cron jobs | Low |\n| Platform move | CMS and templates | URL structure changes silently | Medium |\n| Redesign | Templates and content | Content pruned without redirects | Medium |\n| Domain change | Hostname | Redirect chains, lost authority signals | High |\n| Consolidation | Several sites into one | Duplicate content and\u003Cbr>cannibalisation | High |\n| [HTTPS or URL](HTTPS or URL)[ ](HTTPS or URL)scheme | Protocol or structure | Mixed content, canonical mismatch | Medium |\n\nONE AT A TIME  \nCombining a redesign with a domain change halves your ability to diagnose what went wrong. If the schedule forces both, separate them by at least four weeks so each has its own before-and-after.  \nThis migration  \nTYPE SELECTED WHAT IS DELIBERATELY NOT CHANGING  \nProtects your diagnosis later  \nSECTION 2  \nInventory and baseline  \nCapture these before touching anything. Every one of them is impossible to reconstruct after cutover.  \nBaseline numbers  \n\n| METRIC | SOURCE | VALUE | CAPTURED ON |\n| --- | --- | --- | --- |\n| Indexed pages | Search Console |  |  |\n| Organic clicks, last 28 days | Search Console |  |  |\n| Total sessions, last 28 days | Analytics |  |  |\n| Conversions, last 28 days | Analytics |  |  |\n| Top 20 landing pages | Analytics |  |  |\n| Top 50 ranking terms and positions | Rank tracker |  |  |\n| Referring domains | Backlink tool |  |  |\n| Core Web Vitals, mobile | Field data |  |  |\n\nInventory to export and keep  \n Full crawl of the old site, exported  All indexed URLs from Search Console  \n All URLs with external links pointing at them  Current robots.txt and sitemaps  \n Existing redirect rules already in place  Structured data currently emitted  \n Tracking tags and their trigger conditions  Email and DNS records as they stand today  \nKEEP THE CRAWL FILE  \nArchive the pre-migration crawl somewhere permanent. Six months later, when somebody asks why a page disappeared, it is the only record that it ever existed.  \nSECTION 3  \nThe URL map  \nEvery old URL gets a destination and a decision. No blanks, no bulk redirects to the homepage.  \n\n| OLD URL | DECISION | NEW URL | STA","cbCaio81LZssK6xc","https://ap.wps.com/l/cbCaio81LZssK6xc","pdf",559731,10,"English","# How to use this runbook\n## Migration types and what each risks\n## Inventory and baseline\n## The URL map\n## Pre-cutover build\n## Cutover sequence\n## Rollback plan\n## Post-migration monitoring","[{\"question\":\"What is the biggest predictor of a clean migration?\",\"answer\":\"Whether the URL map was built from a crawl or from someone’s memory of the site.\"},{\"question\":\"Why should baseline numbers be captured before migration?\",\"answer\":\"A migration cannot be proven successful without metrics from before the cutover, and those values are impossible to reconstruct afterward.\"},{\"question\":\"What does the runbook recommend for redirects validation?\",\"answer\":\"Test redirects in bulk using an automated checker against staging, instead of relying on spot checks or sampling.\"}]","Website Migration Runbook - Protect the traffic you already have | PDF",1790118689]