Migrating an existing store

Inventory before changing traffic

Sprytto connects to the existing Tebex store; it does not duplicate packages, prices, tax rules or payment history into a new merchant account. Begin with a read-only inventory of what players use today.

• Record every public URL, navigation entry, package/category destination and external campaign link.
• Export the text and media you are licensed to reuse, but never export secrets into a content file.
• Identify custom scripts or embeds that need a reviewed structured component rather than direct execution.
• Choose a low-risk traffic window and name the person authorized to roll back DNS or the release.

Rebuild and verify privately

Connect Tebex, sync the catalogue and rebuild the storefront on the private development hostname. Use redirects for routes that cannot remain identical.

1. Match categories and package cards to provider IDs from the synchronized catalogue.
2. Recreate global navigation, footer, policy links and localized metadata.
3. Upload approved assets to managed media and replace legacy hotlinks.
4. Create exact or prefix redirects for retired paths, then test query strings and locale routes.
5. Run keyboard, mobile, checkout hand-off and release diagnostics without changing live DNS.

Cut over with rollback

Publish one immutable release before changing the custom domain. Keep the previous store and DNS instructions available until the new hostname, TLS, catalogue and checkout return path are healthy from an external network.

• Reduce DNS TTL only through the domain provider's approved process and early enough to take effect.
• Verify top inbound links, analytics consent, one purchase path and signed webhook processing after cutover.
• Rollback by restoring the previous DNS target or prior Sprytto release according to the prepared criterion.
• Do not delete old assets or redirects until the agreed observation window ends.