Lock-in Assessment
Find out exactly what leaving would cost, before you commit to anything.
Most teams cannot answer a simple question about the platform their reporting runs on: if we had to leave, what would it actually take? Not a gut feel, a number. The assessment exists to replace the gut feel with an inventory.
It is free, it takes two weeks, and it needs read access and nothing else. Nothing is migrated, nothing is changed, and there is no obligation past the report. If you never move a single dataflow, the report is still yours to keep.
What you get
A complete estate inventory
Every Magic ETL dataflow or Alteryx workflow, every dataset, connector, macro, Server artifact, and scheduled job. Not a sample and not an estimate. Teams are routinely surprised by the size of their own estate, because nobody has ever counted it end to end.
A complexity classification per pipeline
Each pipeline is sorted into standard data preparation that transpiles cleanly to SQL, and the smaller slice of dense formula logic that needs closer attention. That split is what makes a fixed price possible, because scope is known before anyone quotes.
A dead and duplicate report
Pipelines feeding reports that no longer exist. Copies made during an old rebrand and never cleaned up. On a mature estate this is regularly a quarter or more of the total, and it is work to retire rather than pay to migrate.
A dependency and lineage map
What feeds what, which external systems are in the path, and where the ordering constraints are. This is the part that usually lives in one senior engineer's head, and it is the part that makes migrations overrun when it is not written down.
A fixed price and a fixed timeline
The number at the end. What the conversion costs, how long it takes, and what the phasing looks like. Quoted as a fixed price, not open-ended time and materials, because the inventory removed the guesswork.
How it runs
- 1
Read access
We connect with read-only credentials scoped to metadata and pipeline definitions. No production data is copied out of your environment.
- 2
The scan
Our scanner walks the estate and extracts every pipeline definition, its transform steps, its inputs and outputs, and its schedule.
- 3
Classification
Each pipeline is scored for migration complexity, and dead or duplicate work is separated out from the pipelines still carrying real business logic.
- 4
The readout
We walk your team through the report: what is in the estate, what is worth migrating, what it costs, and how long it takes. You keep the report either way.
Is this the right step for you?
Good fit
- Any team on Domo or Alteryx that has never inventoried its own estate
- Data leaders heading into a renewal who want a real position at the table
- Organisations where the transformation logic has outlived the people who wrote it
- Anyone who needs a defensible number for a build-versus-stay business case
Probably not
- Teams looking for a dashboard rebuild with no transformation layer underneath
- Estates on platforms we do not yet cover. Ask, and we will tell you honestly
The other steps
We convert the estate, your team stays in the driving seat.
End to end delivery, with a diff report on every pipeline before cutover.
Not sure which applies? Read how it works end to end, or check the questions we get asked.
Find out what leaving would actually cost.
The lock-in assessment is free, takes two weeks, and needs read access. You keep the report whether or not you migrate.