Migration
Migration is a first-class Nona workflow.
The built-in CLI migrator helps you move Firebase Remote Config parameters into:
- a Nona project
- one or more Nona environments
- matching Nona scopes and content types
This is important because moving off Firebase Remote Config is usually not just a data-export task. It is a product-model transition:
- from a hosted control plane
- into a self-hosted runtime config and feature-flag system
When to use this section
Section titled “When to use this section”Use this migration section when:
- you already have Firebase Remote Config in production
- you want to preserve existing parameter work
- you need a structured cutover path
- you need to understand how Firebase concepts translate into Nona concepts
What the migration path covers
Section titled “What the migration path covers”The migration docs help you reason about:
- how Firebase concepts map into Nona concepts
- how values land in environments
- how scopes are assigned
- how boolean flags remain feature flags after import
- how to validate the result before cutover
First command to run
Section titled “First command to run”If you are already at the evaluation stage, start with:
nona migrate firebase --config ./nona.migration.json --dry-runThen continue with Migration validation before production cutover.
Migration mindset
Section titled “Migration mindset”The safest way to approach migration is:
- understand the mapping
- run a dry run
- import into a controlled target
- validate real reads
- only then treat the new system as production-ready
Recommended order
Section titled “Recommended order”Recommended migration sequence
Section titled “Recommended migration sequence”- map the Firebase concepts into Nona’s model
- prepare the migration config file
- run a dry run
- apply the migration
- validate the imported environments and keys
That keeps migration as an operator workflow instead of an ad hoc manual rewrite.
Start here
Section titled “Start here”Is migration just an export and import task?
Section titled “Is migration just an export and import task?”No.
For Nona, migration is also a model transition from Firebase concepts into projects, environments, scopes, and typed entries.
What is the first migration command I should run?
Section titled “What is the first migration command I should run?”Start with a dry run:
nona migrate firebase --config ./nona.migration.json --dry-run
That gives you the safest first look at how the source data will land in Nona.
Do Firebase boolean parameters stay useful after migration?
Section titled “Do Firebase boolean parameters stay useful after migration?”Yes.
Boolean Firebase values map naturally into Nona boolean entries, which means they continue to work as feature flags after import.
When is the migration actually complete?
Section titled “When is the migration actually complete?”Only after you validate environments, scopes, datatypes, and real application reads, not just after the import command succeeds.