Data portability and exit strategy
Banks have to show they can leave a technology provider without disrupting critical services. With Blits.ai you can export your assistants and your data, move from our cloud to your own infrastructure, or take your data elsewhere.
What you can export
Complete assistants
An assistant exports as one package with its flows, intents and training data, functions, and the agents, workflows and model settings it uses. Flows are modelled in BPMN, an open process standard.
Format: encrypted package, importable into any Blits.ai environment
Conversation history
All conversations of an assistant, for analysis, archiving or migration.
Format: CSV
Training data
The intent dataset and its recognition results, so you can retrain on any other platform.
Format: CSV
Knowledge and consent records
Your knowledge base documents stay your own files, and GDPR consent records export per assistant.
Format: original files, CSV
Three ways out
Take the platform in house
Move from our managed cloud to your own private cloud or data center. It is the same platform, so assistants are exported and imported without rebuilding.
Run it yourself
With an on premises setup your team operates the platform, the models and the data, and does not depend on Blits.ai to keep services running.
Move to another provider
Take your conversations, training data and knowledge documents in open formats, and use the BPMN flows as the blueprint for the new build.
An exit plan your auditor will accept
Under DORA, EU financial entities need a documented and tested exit strategy for ICT services that support critical or important functions. Regulators in the Gulf ask for the same. These are the questions to answer for any conversational AI provider, including us.
- 1
Which data can we export, and in which format?
Conversations, training data, knowledge and configuration, and whether the formats are usable outside the platform.
- 2
Can we run it ourselves?
If the provider fails, can the service continue in your own environment, or only with the provider?
- 3
Where are the models?
If the assistant depends on one model provider, the exit plan has to cover that provider too.
- 4
How long does a migration take?
Agree a realistic transition period and test the export at least once a year.
- 5
What happens to our data afterwards?
Agree how and when the provider deletes your data once you have left.
Data portability: FAQ
Want the exit plan before you sign?
We walk your risk team through export, migration and on premises options.
Plan a call