To minimize potential issues when migrating your site:
1. Provide access to a test environment
Share access to a test, preview, or staging version of your new site with our team. It’s essential to test the Fresh Relevance script on the new site before the migration. This allows us to review and update the script if needed.
2. Add the staging site to Event filters
Prevent data from overwriting your product database during testing by adding the new staging URL to Event filters.
To do this:
Expand the User menu, then go to Settings > Website Settings > Activity Block (Test/Office Data).
At the top of the page, in the Enter value field, enter the URL for your staging or test environment.
You can also optionally add a description.Select ADD.
3. Use a catch-all for triggers
Before launching the new site, set your triggers to catch-all to test and verify sends without customers seeing them.
To do this:
Expand the User menu, then go to Settings > Triggers and Messaging integrations > Go Live!
Under Catch-all email addresses, for both All sends (except browse abandon) and Browse abandon, enter an email address.
If you also have SMS sends configured, under Catch-all mobile number, for both All sends (except browse abandon) and Browse abandon, enter a mobile number.
Select SAVE.
Once you’re happy that your triggered messages are working as expected, remove the catch-all email addresses and mobile numbers to re-enable sending triggers to your real visitors.
4. Check web content in the Site editor
Review your content configuration in the Site editor to ensure compatibility with your new platform.
To do this, input the staging site URL in the address bar and browse the new layout. If necessary, you can adjust content placement using the advanced section or delete the current configuration and start from scratch by dragging and dropping content onto the new site layout.
Learn more in The Site editor.