Migrate your Basecamp data

Projects are the top-level container in Basecamp. They hold To-dos, Message Boards, Schedules, Documents, and Files. We preserve the project hierarchy, name, description, archived status, and membership list during migration.

To-dos carry assignee, due date, completion status, and notes. Basecamp does not support sub-subtasks — a flat structure. We map To-dos one-to-one and preserve completion state and assignee assignments.

To-do Lists group To-dos within a Project. We preserve the list name, ordering, and which To-dos belong to which list. If the destination has no equivalent grouping, To-dos land as flat tasks with a custom property indicating the original list.

Message Boards hold discussion threads with title, body, author, timestamps, and comment threads. We flatten the board/thread structure into a series of threaded posts and preserve the comment hierarchy.

Schedule events carry a title, start/end datetime, all-day flag, and assigned person. We map them to calendar tasks in the destination with the same date, time, and assignee data.

Documents in Basecamp are rich-text pages created in Workdocs. We export the full HTML content, title, author, and creation timestamp. Images embedded in Workdocs are downloaded and re-attached as files.

Hill Charts visualize task progress on an implied up-hill curve and are unique to Basecamp. The underlying data is a numeric progress value per To-do. We extract this as a custom numeric field in the destination rather than reproducing the chart itself.

Files attached to To-dos, Messages, or Documents are stored with a download URL and filename. We download each file and attach it to the corresponding record in the destination, handling any size or type restrictions the destination imposes.

Comments attach to To-dos, Messages, and Documents. We preserve the comment text, author, and timestamp, and attach them to the corresponding migrated parent record.

Pings are ephemeral direct messages in Basecamp with no persistent thread archive beyond recent history. These are not reliably exportable via API or built-in export. We flag this as a data loss gap before migration begins.

Project Templates store the structure of a Project — To-do Lists, scheduled items, and initial messages. We replicate the template structure as a new Project in the destination and flag it as a template.

Basecamp charges per active user. Guest collaborators (clients, contractors) do not count toward billing. We preserve the user list, their email addresses, and their role within each project, mapping billing users to active seats in the destination.