Migrating from v1
Where everything from OpsLyft v1 lives in v2, what came across automatically, and what to review.
Nothing needs reconnecting when you move to v2. Your cloud connections, dashboards, saved reports, budgets, integrations, and teammates come with you. Some features moved to new places, and three are new.
Where things moved
| In v1 | In v2 | What's different |
|---|---|---|
| Dashboards | Canvases in Iris | All dashboards came across with their widgets. Iris can read and explain each one. |
| Cost Analyzer | Cost Explorer | Saved reports are now Views, with the same filters and grouping. New: persona lenses, amortised costs, and Analyze. |
| Recommendations | Optimisation | Each saving now has an owner, an effort score, and a ticket. |
| Anomaly alerts | Monitor → Anomalies | Spikes arrive with the resources and owner behind them. |
| Budgets | Budgets & alerts | Same thresholds and recipients. Raise or investigate from the card. |
What's new
| Feature | What it does |
|---|---|
| Iris | Ask in plain English, or describe a dashboard and Iris builds it. |
| Atlas | What changed in your cloud this week, and what each change costs per month. |
| Tickets | Two-way Jira sync. Status comes back without anyone updating it. |
What came across
| Item | Status after migration |
|---|---|
| Cloud connections | All providers keep syncing. Nothing to reconnect. |
| Dashboards → Canvases | Moved. A few may use a v1-only filter and are flagged Need a look. |
| Saved reports → Cost Explorer views | Moved with the same filters and grouping. |
| Budgets & alerts | Kept with the same thresholds and recipients. Budgets that look like tests are flagged. |
| Jira & Slack | Still connected. Jira sync is now two-way. |
| Teammates | Everyone in your org can open v2. You can invite the ones who haven't yet. |
The returning-user flow
The first time you open v2 you see three short steps:
Welcome back
A summary of what came across from v1 and the few things worth a look before your team arrives.
Where things moved
The table above, as cards. Select one to see where it now sits in the v2 sidebar.
Tuned from your v1 habits
OpsLyft suggests a role based on what you opened most in the last 90 days. For example, if you used Recommendations and Budgets most, it suggests FinOps lead. It also offers to open v2 on your most-used v1 dashboards, and asks how you want to learn what's new: a 90-second guided tour, a checklist, or just mark what moved.
Select Skip to v2 at any point to go straight to the workspace.
After you migrate
Review flagged canvases
Open Observe → Canvas and look for canvases marked as needing a look. These use a filter that only existed in v1. Edit the widget filters to use a v2 dimension.
Clean up test budgets
In Monitor → Budgets & alerts, open the Looks like tests group. These budgets are 5× or more below actual spend every period. Delete them or fix the amount.
Turn on the new Jira sync
Two-way sync is on by default for existing Jira connections. Check the status mapping so Jira states map to the ones you expect.
Invite the rest of your team
Share v2 with teammates who haven't opened it yet.
FAQ
Yes. v2 reads the same billing data. If you compare with v1, check that you're using the same cost type. v2 defaults to Amortized.
Yes. Budgets are evaluated by the same budget service as v1, so thresholds and alert timing are unchanged.