/handbook/aem-to-wordpress-migration/launch/
What We Do
Digital Platform MigrationsKey SolutionsManaged ServicesStaffing SolutionsIndustriesProducts
Discovery
Strategic consultancy & project roadmap
Growth Services
On demand development & consultation
Site Maintenance
Annual maintenance. Done for you
QE Services
Testing across SDLC for assured quality
Hosting Migration
Move to a performant hosting with zero downtime
WooCommerce
Enterprise commerce delivered without lock-in
AI
Unlock real use cases and integrations
All Services
A suite of services for any need
Technology STACK
eCommerce
Scale your e-commerce with WooCommerce, integrations, and custom extensions for growth.
EasyEngine
Server management tool that makes using WordPress on Nginx easy.
Web Auditor
Performance Audit & Insights for your Website.
rtMedia
A complete media management plugin for WordPress.
Resources
About Us
CLEAR
Resources AEM to WordPress migration guide The migration process Site launch
Topics
On this page
Work on a deployment checklist
Domain configuration
SSL certificate installation
Permalink and URL settings
Plugin and theme compatibility
Backup plan
A final staging review: A last-minute check-up
Document a go-live procedure
Final server configuration
Caching setup
Database optimization
CDN integration
Switching from staging to production
Activate CDN and caching
Create a rollback plan
Two key elements of a rollback plan
Last updated on May 25, 2026
Launch
The launch phase marks the final stretch of the AEM to WordPress migration journey. It’s where all the planning, development, and testing come together for a successful go-live. This stage includes the final deployment checklists, go-live procedures, and rollback plans.
Work on a deployment checklist
Your deployment checklist serves as pre-launch verification to ensure that everything is ready to go live. This includes reviewing key areas such as server settings, URLs, SEO, and site readiness before going from the staging environment to the live environment.
You can use this deployment checklist to build upon:
Domain configuration
Your domain is the gateway to your website, so it’s essential to ensure it’s properly configured:
- Ensure your domain’s A record is pointing to the correct IP address for your WordPress server.
- Double-check DNS propagation; changes might take up to 48 hours to reflect globally.
A common pitfall:
Rushing DNS changes without verifying can lead to downtime. Tools like What’s My DNS let you monitor the process and ensure everything is resolving correctly.
SSL certificate installation
An SSL certificate encrypts your site, making it safe for users to browse. Beyond security, HTTPS is also a trust signal. Users actually expect to see the padlock icon in their browser bar! So:
- Verify that your SSL certificate is installed and functioning correctly.
- Test URLs to ensure they redirect from HTTP to HTTPS without any issues.
Did you know?
Google flags non-HTTPS sites as “Not Secure,” which can harm your reputation and rankings. A quick SSL test ensures your site stays secure and professional.
Permalink and URL settings
Your URL structure defines how your content is accessed, and it needs to be clean, logical, and consistent. If your previous site had a different URL structure, it’s crucial to set up proper redirects to avoid broken links. We’ve actually already taken care of this during the migration. But link settings should still be checked before going live:
- Review Permalink Settings in WordPress to match your desired URL format.
- Test redirects for legacy URLs, ensuring no valuable SEO equity is lost.
Sampling for consistency
For large datasets, such as 10,000 blog posts, testing 5% for correct taxonomy mapping, media inclusion, and URL consistency before proceeding with the full migration ensures efficient validation.
Plugin and theme compatibility
Your plugins and theme power your site’s functionality and design, but compatibility issues can sometimes arise when moving from staging to production.
- Update all plugins to their latest versions and confirm compatibility with your WordPress version. (You’ve been working on your migration over months—did you miss any updates?)
- Check your theme’s responsiveness across browsers and devices.
Backup plan
Even with the best preparation, things can sometimes go wrong. A backup plan ensures that if the unexpected happens, you can quickly restore your site and minimize downtime.
- Create a full backup of your site, including files and the database.
- Store backups in multiple locations, such as on your server and in cloud storage.
A final staging review: A last-minute check-up
Before flipping the switch to go live, it’s good to give the staging site one final review:
- Remove any test content, such as placeholder posts or dummy data.
- Check key user flows, such as completing a purchase, submitting a form, or signing up for a newsletter.
- Confirm staging and production environments match, small differences can lead to big surprises after launch.
Tip: Having someone outside your team review the site can be invaluable. Fresh eyes often catch issues you might overlook during testing.
Document a go-live procedure
Go-live procedures cover the steps to make the site available for users, coordinate with relevant teams, and communicate the transition to all stakeholders. Here’s a procedure you could build upon:
Final server configuration
Before the big switch, the server needs to be fine-tuned to ensure it performs at its best under real-world conditions. The main focus here is on caching, database optimization, and ensuring everything runs efficiently.
Caching setup
Caching helps serve users quickly without reprocessing everything repeatedly. For this, both page caching and object caching need to be set up. Page caching saves a ready-to-serve version of each page, while object caching, using tools like Redis or Memcached, stores frequent database queries. This ensures visitors experience faster page loads. Review that caching is working correctly.
Database optimization
You don’t want your website to be bogged down by unnecessary clutter in the database. Running optimization commands, like OPTIMIZE TABLE, helps keep the database lean and efficient. It’s like tidying up your workspace so that everything is organized and accessible. Confirm that the database is optimized.
CDN integration
Finally, a Content Delivery Network (CDN), such as Cloudflare, needs to be integrated to speed up content delivery. A CDN ensures that all assets, like images and scripts, are served from a location closest to each user, providing a smooth experience regardless of where they are accessing the site from. Confirm if your CDN integration is working properly.
Switching from staging to production
Now comes the exciting part: moving from staging to the live production environment. This process ensures that what worked in the testing phase transitions smoothly to the real environment.
Back up before you move
Before making any changes, it’s important to create a complete backup of the staging site, including both the files and the database. This serves as a safety net—if anything goes wrong, we can quickly roll back and avoid downtime.
Update the DNS
The next step involves updating DNS records to point the domain name to the new production server. The DNS update may take anywhere between a few minutes to a couple of hours depending on your domain’s TTL (Time to Live) settings, so it’s good to be patient.
Replace staging URLs
After the DNS update, it’s crucial to replace any leftover URLs from staging with production URLs. This can be done easily using WP-CLI to search and replace all references, ensuring there are no broken links or image references that point to the staging environment. This guarantees that users will have a seamless experience without hitting any “not found” errors.
Activate SSL for security
We also need to activate the SSL certificate to make sure the website is accessible securely through HTTPS. This encrypts all data between users and your server, fostering trust and ensuring data privacy.
Activate CDN and caching
Once the site is live, we need to ensure it’s running efficiently and delivering content quickly. Activating the CDN and setting up caching are the keys to making this happen.
Enable CDN for global reach
A CDN helps deliver images, scripts, and other resources quickly to users, no matter where they are. By serving static content from servers closest to users, the CDN greatly reduces load time, ensuring a snappy experience. If you’ve added a CDN to your setup, see that it’s enabled.
Set up page and object caching
Now, let’s make sure caching is properly enabled:
Page caching
It allows the server to serve pages instantly without recreating them every time.
Object caching
Using tools like Redis, stores database query results in memory so that future requests can be served faster.
Testing the caching
After enabling caching, it’s crucial to verify it’s working. A simple command like curl -I https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.example.com can help check if headers such as Cache-Control or X-Cache are set correctly, indicating that caching is functioning as expected. Additionally, tools like GTmetrix or Pingdom can help assess the performance and verify that assets are being served from the CDN.
Create a rollback plan
Even with the most thorough planning, unexpected issues can arise once a website goes live. That’s why a solid rollback plan is essential. It provides a safety net that ensures you can revert to a stable version quickly if any issues occur. The goal of a rollback plan is not just to “go back,” but to do it efficiently, minimizing downtime and preserving data integrity.
Two key elements of a rollback plan
1. Backup verification
The first and most crucial part of the rollback plan is to verify your backups. Before launching, ensure that full backups of the website are available; this includes both the files and the database. It’s not just about creating a backup but also verifying its completeness and usability. These backups should be stored securely, ideally in multiple locations (local and cloud storage), so they can be accessed easily if needed.
Testing the restoration process is also key. A backup that can’t be restored effectively is as good as no backup at all. Perform a test restore in a sandbox environment to verify that the backup can be used without issues.
2. Reversion strategy: Planning the path back
The reversion strategy outlines the steps to follow if things don’t go as planned after the launch. The goal is to minimize disruption to users and bring the website back to a stable state as smoothly as possible. Here’s what your reversion strategy could look like:
- Restoring from a backup: If an issue arises, the most direct approach is to restore the backup taken from the staging or production environment. This ensures that the site reverts to its last known stable state. Using backup tools that support automated restoration can speed up this process and minimize downtime.
- Restoring to an earlier version using a version control system: If the issues relate specifically to some code or design changes, then reverting to a previous commit via a version control system like Git is an efficient approach. Rolling back to a stable commit is often faster and more controlled compared to restoring the entire site.
- Keeping the previous AEM environment on standby: During the initial days post-launch, it’s wise to keep a copy of the previous AEM environment readily available as a fallback. This way, if the new WordPress site experiences significant issues, the AEM site can be temporarily reinstated while you work on resolving problems. This serves as an ultimate failsafe, especially during the crucial early period when unexpected bugs or performance issues are most likely to surface.
With all these resources, you’re now ready to publish your new WordPress stack! Once you successfully launch your new WordPress website, you enter the post-migration phase.
Post-migration essentials
NEXT
Credits
Disha Sharma
Author
Disha Sharma
Author
Disha Sharma is a Content Writer at rtCamp with over a decade of experience at the intersection of technology, digital marketing, and enterprise content strategy. Her WordPress roots run deep, her …
Shreya Agarwal
Author
Shreya Agarwal
Author
Shreya Agarwal is a Growth Engineer at rtCamp, she brings active, hands-on WordPress development credentials to everything she writes and reviews. A WordPress Core Contributor with merged pull requ…
Good Work. Good People.
Industry partnerships
Compliance certifications
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Company
Solutions
Subscribe to our newsletter and get a few email updates every month.
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Cookie Consent
We value your privacy
We use cookies to give you the best possible experience. By clicking “Accept,” you consent to our use of cookies to improve site functionality, analyze usage, and personalize content and communications. Your privacy matters to us, and we are committed to handling your data responsibly and transparently. Please check our Privacy Policy for more details.
Manage PreferencesDon’t AllowAllow All
Why do we use cookies?
×
By clicking "Accept" or "Decline All" at the bottom, you consent to the use of cookies and other tools as described in our Cookie Policy in accordance with your settings and accept our Terms of Service.
Toggle EssentialEssential
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Geolocation Config
This cookie is used to store the consent settings based on the visitor's location.
30 days
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
Toggle CloudFlareCloudFlare
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Service URL: developers.cloudflare.com (opens in a new window)
Name
Description
Duration
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
Toggle CommentsComments
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Toggle GodamGodam
GoDAM" is primarily a specialized WordPress plugin and media management service designed to enhance video hosting, marketing, and asset management directly within the WordPress dashboard.
Service URL: godam.io (opens in a new window)
Name
Description
Duration
user_image
Temporarily stores the path to the user's avatar or profile picture for quick rendering in the website header.
session
user_id
Stores the numerical ID of the logged-in user to maintain session continuity and basic site operations.
session
full_name
Stores the logged-in user's display name to personalize the site interface without needing database queries.
session
system_user
First-party cookie used to store basic application state identifying the current system user role.
session
sid
A generic session ID cookie used to maintain user state and functionality as the visitor navigates through the site.
session
Toggle Google reCAPTCHAGoogle reCAPTCHA
Google reCAPTCHA helps protect websites from spam and abuse by verifying user interactions through challenges.
Name
Description
Duration
_GRECAPTCHA
Google reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis.
179 days
Toggle Google Tag ManagerGoogle Tag Manager
Google Tag Manager simplifies the management of marketing tags on your website without code changes.
Name
Description
Duration
cookiePreferences
Registers cookie preferences of a user
2 years
td
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
session
Toggle StatisticsStatistics
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Toggle Factors AIFactors AI
Factors.ai is a B2B account intelligence and marketing analytics platform that helps Go-To-Market (GTM) teams identify anonymous website visitors, track buyer journeys, and measure the ROI of marketing campaigns.
Service URL: www.factors.ai (opens in a new window)
Name
Description
Duration
_fuid
It is sent to capture session details and track user behavior across your website to provide behavioral data and intent signals.
1 Year
Toggle Google AnalyticsGoogle Analytics
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com (opens in a new window)
Name
Description
Duration
FPGSID
Stores a session or user identifier to track how visitors interact with a website. This helps Google Analytics measure website performance, user engagement, and usage patterns.
Session
FPLC
Used by Google Analytics to link visitor interactions and sessions across multiple related domains.
20 hours
FPID
A server-side Google Analytics cookie used as an alternative user identifier when third-party cookies are restricted.
2 years
_ga
ID used to identify users
2 years
_ga_
ID used to identify users
2 years
Toggle Jetpack StatsJetpack Stats
Jetpack's built-in visitor analytics. It records page views, referring sites, search terms, and outbound link clicks, and also carries the shared visitor-tracking library used by Jetpack Instant Search and WooCommerce Analytics.
Service URL: automattic.com (opens in a new window)
Name
Description
Duration
tk_aip
Stores a list of anonymous visitor IDs so they can be merged into one identity once a visitor is recognized.
Up to 5 years
tk_tc
Used once per page load to work out which cookie domain the Tracks library should use, then removed as soon as it's read back.
Session (deleted immediately after use)
tk_qs
Queues analytics events for Jetpack's Tracks library so none are lost if the page closes before they can be sent.
30 minutes
tk_ai
Stores a randomly-generated anonymous visitor ID so Jetpack's Tracks analytics library can link tracking events to the same visitor.
Session in wp-admin; up to 5 years on the frontend
Toggle Microsoft ClarityMicrosoft Clarity
Clarity is a web analytics service that tracks and reports website traffic.
Service URL: clarity.microsoft.com (opens in a new window)
Name
Description
Duration
CLID
Identifies the first-time Clarity saw this user on any site using Clarity.
12 months
ANONCHK
Indicates whether MUID is transferred to ANID, a cookie used for advertising. Clarity doesn't use ANID and so this is always set to 0.
Session
_clck
Persists the Clarity User ID and preferences, unique to that site is attributed to the same user ID.
12 months
_clsk
Connects multiple page views by a user into a single Clarity session recording.
12 months
Toggle Parse.lyParse.ly
Parse.ly is a content analytics platform that helps publishers optimize audience engagement and content performance.
Name
Description
Duration
cookies.js_dtest
This cookie determines whether the browser accepts cookies.
session
_parsely_session
JSON document storing information identifying a browsing session according to Parsely’s proprietary definition
30 minutes
_parsely_visitor
JSON document uniquely identifying a browser and counting its sessions
13 months
Toggle SalespanelSalespanel
Salespanel is a B2B marketing and sales software that identifies, tracks, and qualifies website visitors and leads in real-time using first-party data. It helps businesses monitor customer journeys, score leads based on behavior, and syncs this data with CRMs (like Pipedrive or HubSpot) to improve conversion rates.
Service URL: salespanel.io (opens in a new window)
Name
Description
Duration
track_uid
Identify and tracking a lead
12 moths
Toggle MarketingMarketing
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Toggle Bing / MicrosoftBing / Microsoft
Bing, powered by Microsoft, is a search engine providing web, image, video, and map search capabilities.
Name
Description
Duration
MR
Used to collect information for analytics purposes.
6 months
ANONCHK
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
10 minutes
SM
Used by Microsoft in synchronizing the MUID across multiple Microsoft domains to track users for advertising.
session
MUID
Identifies unique web browsers visiting Microsoft sites. These cookies are used for advertising, site analytics, and other operational purposes.
1 year
Toggle DoubleClick/Google MarketingDoubleClick/Google Marketing
A comprehensive digital advertising platform for managing campaigns, optimizing performance, and analyzing audience data.
Name
Description
Duration
IDE
This cookie is used for targeting, analyzing and optimisation of ad campaigns in DoubleClick/Google Marketing Suite
2 years
ar_debug
Store and track conversions
Persistent
Toggle LinkedInLinkedIn
LinkedIn is a professional networking platform for job seekers, employers, and industry connections.
Name
Description
Duration
bscookie
Used by LinkedIn to track the use of embedded services.
1 year
AnalyticsSyncHistory
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries
30 days
bcookie
Used by LinkedIn to track the use of embedded services.
1 year
li_sugr
Used to make a probabilistic match of a user's identity outside the Designated Countries
90 days
lidc
Used by the social networking service, LinkedIn, for tracking the use of embedded services.
1 day
UserMatchHistory
Used by LinkedIn Ads to synchronize and match user IDs across different ad networks and data providers.
30 days
Toggle LinkedIn InsightLinkedIn Insight
LinkedIn Insight is a web analytics service that tracks and reports website traffic.
Service URL: www.linkedin.com (opens in a new window)
Name
Description
Duration
li_sugr
Used to make a probabilistic match of a user's identity.
90 days
lidc
Used for routing and session management.
24 hours
Toggle LiveIntentLiveIntent
LiveIntent provides a platform for email advertising and identity-driven marketing solutions.
Name
Description
Duration
_lc2_fpi_js
Companion cookie to _lc2_fpi used by JavaScript to facilitate cross-domain ad tracking and user identification.
1 year
_lc2_fpi
First-party tracking cookie usually associated with LiveRamp to identify users across devices for targeted advertising.
1 Year
_li_ss
Sets a unique ID for the visitor, that allows third party advertisers to target the visitor with relevant advertisement. This pairing service is provided by third party advertisement hubs, which facilitates real-time bidding for advertisers.
1 month
lidid
Collects data on visitors' behaviour and interaction - This is used to make advertisement on the website more relevant. The cookie also allows the website to detect any referrals from other websites.
2 years
Toggle Cookie PolicyCookie Policy
You can find more information in our Privacy Policy.
Allow AllDecline All
Accept