Migrate from Basecamp to monday Work Management

Basecamp Projects map to monday.com Boards. During scoping we determine whether each Basecamp Project becomes its own monday.com Board (preserving 1:1 structure) or whether multiple smaller Basecamp Projects consolidate into a single Board with Groups for each original project. The customer's workflow and team ownership model drives this decision. Project description, archived status, and membership all migrate.

Basecamp To-do Lists map to monday.com Groups. Group name, ordering, and parent project membership transfer. If the destination Board was created as a consolidated workspace rather than a 1:1 project clone, each Group name carries the original To-do List name so reviewers can identify the source structure. Group color and collapse state are configured as part of the workspace setup.

Basecamp To-dos map to monday.com Items. Assignee, due date, completion status, notes, and creation timestamp all transfer. monday.com Status columns map from Basecamp's completed/active state. The to-do's position within the To-do List becomes its item position within the monday.com Group. Basecamp does not support sub-subtasks; if pseudo-subtask patterns exist as separate To-dos in separate Lists, they migrate as flat items and we document the flattening.

Basecamp Message Boards hold discussion threads with a title, rich-text body, author, timestamps, and comment threads. We flatten the board/thread structure by creating a monday.com Item per thread with the thread title as the Item name and the thread body as the Item description. Comment threads attach as Updates on the Item, preserving author, timestamp, and content. The board name becomes the Group name in the destination Board.

Basecamp Schedule Events (title, start datetime, end datetime, all-day flag, assigned person) map to monday.com Items with a Date column populated from the event start and an optional End Date column if the event spans multiple days. All-day events set the Date column all-day flag. Event location migrates as a text column. Assigned person resolves to a monday.com team member.

Basecamp Documents are rich-text pages with title, HTML body, author, and creation timestamp. We export the HTML content and populate the monday.com Item's description with the same content, preserving headings, lists, bold/italic formatting, and embedded image URLs. Images referenced in the HTML are downloaded and re-attached as monday.com file uploads linked to the Item. Author and creation timestamp migrate as custom columns.

Hill Charts are unique to Basecamp and visualize task momentum on an implied up-hill curve. The underlying data is a single numeric progress value per To-do (0-100). The curve itself cannot be exported. We extract the numeric value and populate a custom Number column in monday.com labeled Hill Chart Progress so reviewers can see the original momentum reading. The visual curve does not migrate; teams should be briefed that the chart shape is lost during scoping.

Files attached to To-dos, Messages, or Documents are downloaded from Basecamp using the attachment download URL and filename. Each file is re-attached to the corresponding monday.com Item via the monday.com Files column. We handle file size and type constraints during the download phase and flag any files that exceed monday.com's upload limits. Attachments that were embedded in Basecamp Documents are downloaded and re-attached as individual file references on the migrated Item.

Comments on To-dos, Messages, and Documents attach to the migrated parent record. The comment text, author, and timestamp transfer as monday.com Updates with the author attributed to the relevant team member. Comment threading (if used in Basecamp) flattens to a chronological Update stream, preserving content and timestamp ordering but not the nested reply depth.

Basecamp user email addresses, names, and project roles (admin, member, guest) map to monday.com Team Members. Guests in Basecamp (clients, contractors) map to monday.com Guests, who can be invited at no additional cost on Standard and above. We preserve the project-level role by setting monday.com Workspace permissions per board or by assigning a custom role column so that the original access hierarchy is documented for the customer's admin.

Basecamp Project Templates store a reusable project structure (To-do Lists, scheduled items, initial messages). The Basecamp Classic API does not expose Templates programmatically. We document the template structure (list of To-do Lists, scheduled event titles, and message topics) in a written handoff document so the customer's admin can re-create the template in monday.com using monday.com's Board Templates feature. This is a manual rebuild step outside data migration scope.

Basecamp Pings are ephemeral direct message threads with no persistent archive beyond recent history. They are not accessible via Basecamp API or the built-in export. We flag this as a data loss gap during scoping and recommend that teams export or screenshot any Pings they need to retain before migration begins. This gap applies to all migration directions from Basecamp.