- Self-serve where every competitor ships concierge-only
- Deterministic preset-driven mapping, no AI guesswork
- 24-hour full-job undo from the admin panel
- One-click full export to machine-readable JSON, any time
- Export coverage enforced by a test
- No cancellation cliff: lapsing never deletes your data
Self-serve migration
Most coaching platforms advertise "manual data migration" as a paid concierge service. Coaches send a CSV to a support email and wait days for someone to import it by hand. Colossus runs the import in the dashboard. Upload the file, pick the source preset, confirm the mapping, hit import.
Hand-coded mapping you can audit
Mapping is hand-coded presets, heuristics, and a manual override step where you can fix any row the platform isn't confident about. We don't run an LLM over your client data to guess the schema. The mapping is auditable, repeatable, and free of the hallucinations AI-driven imports are notorious for on edge cases.
One-tap undo for 24 hours
The import job tracks every row it creates. If you spot something off, a single click reverts the whole job inside the 24-hour window. After that, the import is permanent, but you've had a full day to catch any mistakes.
90-day payload retention
The raw upload sits in storage for 90 days, then a scheduled job strips the payload and keeps only the audit metadata. Your client list, scrubbed from the import tooling, lives only in the places you would expect it to live.
The door swings both ways
Every platform makes it easy to move in. The question worth asking before you commit a business to one is what happens when you want to move out, and on most of them the answer is a support ticket, a wait, and a partial spreadsheet.
Colossus exports everything we hold about you as machine-readable JSON, from your account settings, on demand. No ticket, no queue, no fee. The same button is there whether you have been with us a week or five years.
What makes that a promise rather than a feature is how the coverage is maintained. A test walks the whole database schema on every build, and any table holding data linked to a person must either be in the export or be listed as excluded with a written reason. There are 181 in the export today. A new one cannot be added without someone making that decision, which is how an export stays complete instead of quietly falling behind the product.
There is also no cancellation cliff. Letting a subscription lapse switches off your coaching tools; it does not touch your data, and the export keeps working. Deleting your account is a separate, deliberate action that only you can take, and when you take it we delete the files too, not just the rows.