How to Migrate from KoboToolbox to ODK Central
The safest KoboToolbox migration path is export first, test second, and cut over only after the same XLSForm works on the new ODK Central server. KoboToolbox and ODK share the XLSForm ecosystem, so many forms move with little or no redesign; platform-specific settings and media still require testing.
Last reviewed: August 13, 2026. Always preserve an untouched export of the original project before changing forms or data.
What to export from KoboToolbox
Create a migration folder containing:
- The current XLSForm or downloaded form definition.
- Submission data in CSV or XLSX format.
- Media attachments and the mapping between media filenames and records.
- Form IDs, project names, language information, and deployment notes.
- User, permission, and enumerator documentation.
- Any calculated-field, API, dashboard, or integration dependencies.
Do not treat a CSV export as a complete replacement for the original project. Keep the original export and document what the new server will and will not reproduce.
A five-step migration
Test the parts that usually break
Test repeats, choice filters, required fields, calculations, translations, media, GPS, and the final export. A form can validate while still confusing an enumerator because a translation, appearance, or media reference behaves differently on the device.
Run one interview in airplane mode. Then reconnect, send it, open the record in Central, download the data, and compare the result with the original KoboToolbox export. This is more useful than comparing screenshots of form builders.
Why managed ODK hosting reduces migration risk
If the reason for moving is hosting control or KoboToolbox limits, a managed ODK Central server keeps the standards-based workflow without making the migration lead become a Linux administrator. LooprAI can also help inspect, repair, or translate an XLSForm before the pilot.
For the platform decision behind the move, read ODK vs KoboToolbox. If the team is comparing managed options, see the best KoboToolbox alternatives.
Create the new ODK serverFrequently Asked Questions
Can KoboToolbox forms run on ODK Central?
Often, yes. KoboToolbox and ODK Central use the XLSForm and XForm ecosystem, so many forms transfer with little or no redesign. Test choice filters, repeats, translations, media, calculations, and platform-specific settings before the cutover.
How do I export KoboToolbox submissions?
Export the current submissions in a usable data format, download media attachments, and retain the original project documentation. The exact export options depend on the KoboToolbox project and should be checked before migration.
Will KoboToolbox media move automatically to ODK?
Do not assume media will move automatically. Download the media, preserve filenames and record mappings, upload required form media to the destination, and test a complete submission with attachments before cutover.
Should I migrate KoboToolbox during fieldwork?
Avoid a hard cutover during an active round unless the risk is understood and the team can run a parallel pilot. Finish or document in-flight submissions, test the new server, and choose a clear transition date.
Can SurveyLoopr host migrated KoboToolbox forms?
Yes. Deploy a SurveyLoopr-managed ODK Central server, upload the portable XLSForm, validate it, and publish it to the new project. SurveyLoopr does not replace your exported historical data; retain that archive separately.
Is migration from KoboToolbox reversible?
The form workflow is portable when the XLSForm and exports are preserved. Keep the original KoboToolbox project and a tested export so the team can redeploy or compare records if the new workflow needs correction.
No Credit Card Required
Build the form first. Add hosting when you need it.
Start free with LooprAI, then deploy a managed ODK Central server or run DataSnap checks when your project is ready.
Automation handles the mechanical work.
Researchers decide what the evidence means.