Team Workspace Migration to Airtable
17,000+ tasks moved into one Airtable workspace
A company's marketing and events teams ran hundreds of projects in a work-management tool whose contract was ending. I built a Python migration toolkit that moved the active projects into Airtable with their tasks, comments and files, archived the finished ones in a read-only base, and built the interfaces and automations the teams now use for tasks and requests.
By Jin Longyu·Published
The context
Contract ending
Hundreds of projects had to leave the old tool before a fixed date.
History that matters
Comments, attachments and subtasks had to arrive intact, with a record of what moved.
Many teams, one base
Each team worked its own way, and requests between teams went by hand.
How I built it
Migration toolkit
A Python pipeline per project that logs every record, so any project can be re-run and checked.
Rehearsed cutover
Several full test runs, then a wipe-and-rebuild cutover on the day.
Read-only archive
Finished projects moved to a separate base before the old tool was switched off.
Team workspace
Airtable interfaces for tasks, requests between teams and approvals.
Airtable
