Moving F&O configuration from sandbox to production without re-keying it

Configuration is tested in a sandbox and then typed into production again by hand, which is where it breaks. Here's how to move it as data without skipping the review it passed.

Re-keying is where configuration breaks

A parameter change is usually proven in a sandbox: the setting is changed, the process is tested, everyone agrees. Then someone reproduces it in production, page by page and company by company, from a spreadsheet or screenshots, often during the cutover itself. The tested configuration and the production configuration are then two different things that are only meant to be the same, and a typo on the day costs more than any test caught.

A straight import is not the answer

Moving the settings as data sounds better, but an import that writes straight into the live parameter tables skips the review the change went through in the sandbox, and applies it the instant the import runs. Internal record ids also differ between environments, so a setting that refers to another record by its id can land pointing at the wrong one.

Move the version, then review it again

The safer pattern moves a version of the configuration rather than the live values. The version is matched by its name, not a record id, so it reattaches correctly in the target. It arrives as a draft that cannot activate itself, so the target environment's administrator compares it with what is live there, activates it and publishes it. Promotion then ends with the same review and the same audit record as any other change.

Be clear about what cannot travel

Some settings cannot cross environments as values: references stored as internal record ids, financial dimension fields and fields stored as arrays. Those should keep the target's own values rather than arrive wrong. This is how Ballast moves configuration: its versions and every governed table are Data management entities keyed by version name, imports land as drafts, and what does not travel is left as it is in the target, so nothing is re-keyed and nothing skips review.