Skip to main content
Back to Blog
deployment configuration migration workflow

Configuration Migration Between Environments

Swifty Team Nov 30, 2025 2 min read

Building and testing changes to your workspace configuration in a staging environment is good practice. Moving those changes to production reliably is the harder part — until now.

Configuration migration between environments is now a built-in capability.

The Problem It Solves

Without a migration system, promoting configuration changes from staging to production means manually recreating every definition change — every new field, every modified workflow, every updated form layout — in the production environment. This is time-consuming and error-prone. Differences inevitably creep in.

The alternative — making changes directly in production — removes the safety net of testing first.

How It Works

Configuration is exported as a structured package from your staging workspace. The package includes all definition changes: object types, field definitions, workflow configurations, screen layouts, permission rules. Data is not included — only configuration.

The package is then imported into the production workspace. Before applying, the system shows a preview: what will be added, what will be changed, what conflicts exist with the current production configuration.

Conflict Detection

If production has been modified since the staging environment was last synced, conflicts are detected and surfaced. You can review each conflict and decide how to resolve it: take the staging version, keep the production version, or merge manually.

The import doesn't proceed until all conflicts are resolved. You never accidentally overwrite a production change you meant to keep.

Rollback

Configuration changes applied from an import can be rolled back. If something unexpected happens in production after an import, reverting to the previous state is a single action.

The Result

Configuration promotion becomes a deliberate, reviewable, reversible process rather than a manual, error-prone one. Test in staging. Promote with confidence. Roll back if needed.

That's the workflow professional operations deserve.

Related posts

Composed Data Sources

Chain and relate data sources for rich dashboards — compose complex data views from simpler sources without writing code.

Computed Expressions

Transform data with template expressions and built-in functions — format, combine, and derive values from your data without code.

Cross-Source Data Joins

Combine data from multiple sources in one view — join records from your database with data from external services using a shared key.