Read-only by default.
How we handle access, metadata and data during an engagement — starting with the least we need, and nothing more.
Starting with metadata
The free estate scan and most of an estate assessment work from a read-only metadata export. It describes your datasets, calculations, dashboards and permissions — not the business data inside them. No access to your BI platforms is needed at this stage.
Access during a migration
When a migration needs access to a source or target platform, that access is:
- Scoped to what the current phase needs, and agreed in writing beforehand.
- Read-only on the source platform wherever possible.
- Named, so you can see who has it and why.
- Removed when the phase ends.
Where your data stays
- Open specifications are delivered into your repository.
- Regenerated artifacts are deployed into your target environment.
- Parity tests compare results for the same slices on source and target. Wherever possible, they run inside your environment.
Confidentiality
A mutual NDA is standard for every engagement, starting before the first metadata export is shared.
Reporting a security issue
If you believe you’ve found a security issue affecting BITransition, please tell us through our contact page and choose “Something else”. We’ll follow up directly.
See also: privacy and risk & governance.
Show us your estate.
A read-only metadata export is enough to start. No platform access required, mutual NDA as standard.