rocketGuide: Dev-to-Production Deployment

Checklist for moving your Limio configuration from a development environment to production.

This guide covers what to expect when promoting your Limio setup from a development (dev/staging) environment to production.

circle-info

Limio can migrate your data for you. Catalog, offers, campaigns, pages, and components can all be copied from your dev environment to production via a support request to [email protected]envelope. Tenant-level settings are also carried over. You do not need to recreate these manually.

What you need to reconfigure

After Limio migrates your data, anything that references external endpoints, domains, or credentials must be updated to point to your production systems. The general rule: Limio copies your configuration, but you must supply production-specific connection details.

Integrations

All integrations must be reconnected with production credentials and endpoints:

Integration
What to update

Salesforce

Connected App credentials (production org), callback URLs, any org-specific record type names

Zuora

API credentials (production tenant), payment gateway, HPM page domain

Webhooks

All destination URLs must point to production endpoints, plus any authentication credentials

SSO / OIDC

Issuer URL, Client ID/Secret, redirect URIs — all must reference the production domain

See SSO Your Authenticationarrow-up-right for OIDC setup details.

Domain-dependent features

If your production environment uses a different domain (e.g. a custom domain instead of {tenant}-shop.prod.limio.com), update:

If any of your components have hardcoded URLs or links stored in component props (e.g. terms & conditions links, external redirect URLs, image sources), these must be updated to production URLs after migration. Review your pages in Page Builder to check for any dev/staging URLs.

Testing checklist

Before going live, test the following end-to-end in production:

Last updated

Was this helpful?