
Platform · Switching to ToldUntold
Switching platforms sounds like a project nobody has time for, so we built the switch around one rule: to ask you for as little as possible, and adapt to your reality for everything else.
This page tells you what you bring, what we do with it, and what actually changes for the people on the floor.
The ledger
Everything else is us adapting to what you already have: your objectives, your documents, your content, your catalogue, your identity, in the shape they are in today. The three columns below are the whole switch.
As it is, where it is.
Our side of the table.
The first morning.
Import
The training material you spent years writing keeps its value. A PDF, a deck or a video uploads as it is; AI proposes chapters, descriptions and quizzes; your team reviews and publishes.
A folder of slides becomes a program an advisor can follow on a phone, in the language of their market.
Integrations
Little of the switch needs your IT team's calendar. The catalogue and the points of sale come in on our side, and the rest lands in one of three places: native, through the API, or built on request.
Native covers single sign-on, SAML 2.0 and OIDC configured in the admin; Okta, Microsoft Entra ID and Google Workspace all connect this way. The API is there for the day your team wants to automate: server-to-server with scoped keys, employee data in from your HRIS, learning analytics out to your BI tools. The documentation is public and a sandbox is a request away.
Built on request covers the rest, Slack and Teams notifications among them. We scope the work with your IT team, build it, then monitor it while it runs.
Questions
Your content does not get lost: it reimports into ToldUntold and becomes structured programs. The records in your current tool can come out through its own exports and stay archived on your side.
Whether past completions can carry over depends on what that tool exports, so we look at yours case by case and give you a straight answer before anything moves.
It depends on the volume: how much content, how many markets, how many identities. Rather than quote a number before looking, we go through what you have first and put the dates in writing.
We do, with you. The import runs on our side, and so do the catalogue and the translations. Your side makes the calls: what is worth bringing, who gets which role, what goes live first.
PDF, PPTX and MP4, as they are. AI structures them into chapters, descriptions and quizzes, and your team reviews everything before it publishes. The catalogue and the points of sale come in on our side, so your IT team has nothing to schedule.
They come with you. We take your SCORM packages and whatever sits in your current LMS and reshape it into the platform's formats: programs with chapters and quizzes, and episodes where a subject works better short.
Your team reviews the result before anything publishes, so what was worth keeping stays and what had aged can finally go.
No. Content is reimported rather than moved, so the original files stay where they are and the tool you run today is not disturbed. Preparation happens while the contract runs out; when it ends, your teams open an app that already holds their programs, with their accounts ready.