Migrating Projects

When migrating between Logfire projects (e.g., moving to a new organization, testing a new setup), you can double-write data to both projects during the transition period.

Configuration

Using Python

import logfire

logfire.configure(
    token=['pylf_v1_us_old_project_token', 'pylf_v1_us_new_project_token'],
)

Using Environment Variables

Terminal

export LOGFIRE_TOKEN=pylf_v1_us_old_project_token,pylf_v1_us_new_project_token

All traces, metrics, and logs will now be sent to both projects.

How It Works

Each token creates its own independent export pipeline with:

Separate HTTP session (independent retry queues)
Separate span processor for traces
Separate metric reader for metrics
Separate log processor for logs

All telemetry data (spans, metrics, logs) is sent to all configured projects simultaneously.

Completing the Migration

Once you’ve verified data is flowing correctly to the new project:

Remove the old token from the list
Update your environment variable to only include the new token

import logfire

# After migration is complete
logfire.configure(
    token='pylf_v1_us_new_project_token',
)

Or:

Terminal

export LOGFIRE_TOKEN=pylf_v1_us_new_project_token

You may want to wait one full retention cycle of double writing to ensure you have a full dataset in the new project before removing the old token.

Migrating Dashboards, Alerts, etc.

We do not currently have an automated way to migrate dashboards, alerts, or other configurations between projects. You will need to manually recreate these in the new project.

We offer functionality to export and import dashboards via JSON files. Refer to the Dashboard Management guide for more details on exporting and importing dashboards.

We plan to ease this transition by providing IaC (Infrastructure as Code) support in the future.

If you have any questions or need assistance during your migration, please reach out.