1. Preparation Phase (Before DNS Swap)
- Backup Data: Ensure that all website data, content, and configurations are backed up from the current site.
- Check DNS Settings: Confirm the DNS settings for the new domain are ready and correct before making any changes.
- Set Up Reverse Proxy: Implement reverse proxy on the server to avoid service disruption while the DNS swap is in progress. This ensures requests for the current site are redirected seamlessly to the new domain.
2. Website Migration (Current site to New domain)
- Move Content: Migrate all the website content from the current site to the new domain. This includes transferring media, text, database entries, and other assets.
- Update Configurations: Update internal configurations, links, and references within the content to reflect the new domain.
- Test Website: Ensure that the new site(new domain) is fully functional before the DNS update.
3. App Build Updates (FireTV, RokuTV, Android TV)
- Update Base URL in App: Modify the app’s base URL to use a new URL instead of the current site URL.
- Rebuild Apps: Rebuild the updated app versions to reflect the new domain settings. Ensure that any other necessary updates (e.g., bug fixes, and feature updates) are also incorporated into the new builds.
- App Store Review Process: Submit the updated app builds to the respective app stores (Amazon App Store, Roku Channel Store, Google Play Store, etc.) for review. Ensure the new build passes the review process and is approved for release.
4. DNS Swap and Propagation
- Initiate DNS Swap: Change the DNS settings to point the current domain to the new domain. This is the point where crashes are expected in the apps due to the base URL change.
- Monitor DNS Propagation: DNS propagation can take anywhere from 24 to 48 hours. During this time, ensure that both the current site and the new site are running in parallel (via reverse proxy) to prevent downtime for users.
- Monitor App Crashes: Track app crashes and ensure users are directed to the new site during the propagation period.
5. Post DNS Propagation (After 24-48 Hours)
- Confirm DNS Update: After DNS propagation is complete, confirm that all users are now redirected to the new site.
- Remove the current site from the Server: Once everything is stable, and both the website and apps are functioning with the new site URL, remove the current site from the server to avoid conflicts.
6. Final Testing and Validation
- Test Websites: Ensure that the new site is fully operational, with no links pointing to the current site.
- Test Apps: Confirm that apps (FireTV, RokuTV, Android TV) are fully operational with the new base URL and are not experiencing crashes.
- User Experience Check: Ensure that the user experience remains seamless and that no issues arise from the domain switch.