Migrate from Basecamp to Jira

Basecamp Projects map one-to-one to Jira Projects. We preserve the project name, description, archived status, and the project's membership list. In Jira, we configure the project using either the Team-managed or Company-managed template depending on whether the customer plans to use company-wide shared configurations; this choice is made during scoping because it affects how Issue types, workflows, and custom fields are organized. If the Basecamp project contains a large document library, we create a Confluence space as a companion destination and link it from the Jira project description.

Basecamp To-dos map to Jira Issues. Assignee, due date, completion status, and notes migrate directly. We default To-dos to Jira Issue type Story unless the customer indicates the work is non-story (operations, maintenance, admin tasks) in which case we map to Task. Completion state in Basecamp maps to Done status in Jira. Because Basecamp has no subtask support, every To-do becomes a standalone Jira Issue — there is no hierarchy collapse required. The original To-do notes become the Jira Issue description, preserving any markdown formatting.

Basecamp To-do Lists are grouping containers with no direct Jira equivalent. We map them to Jira Epics by default so that the To-do List name becomes the Epic summary and the contained To-dos link as child Stories under the Epic via a parent-link relationship. If the customer's workflow uses To-do Lists as labels rather than containers, we instead add the To-do List name as a Label field on each child Issue. The choice between Epic mapping and Label mapping is made during scoping based on the customer's intended Jira workflow.

Basecamp Message Boards are discussion threads with a title and comment tree. Jira has no native Message Board construct. We flatten the board into the Jira Project by creating a pinned Project-level Comment or by appending the board content to the Jira Project description. The board thread title becomes a section header; each reply becomes a bullet point with author and timestamp. If the board contains fewer than 20 messages, we create a single Jira Issue of type Task with the full board content in the description and each reply as a Comment on that Issue. We document the board-thread hierarchy as a comment on the Issue so the customer can reconstruct the original conversational structure.

Basecamp Schedule events carry a title, start/end datetime, all-day flag, and assigned person. Jira does not have a native calendar event object separate from Issues. We create a Jira Issue of type Task for each Basecamp Schedule event, set the Start Date and Due Date from the schedule data, and attach the event details (location, description, all-day flag) as Issue metadata. Recurring schedule patterns in Basecamp are not programmatically accessible via API — we document the recurring pattern and the customer rebuilds the schedule as a Jira Automation rule or calendar integration post-migration.

Hill Chart numeric progress values migrate to a Jira custom field of type Number or Percentage (customer's choice during scoping). The Hill Chart curve itself is a proprietary visualization that cannot be exported — only the numeric progress per To-do is available via API. We attach the numeric value as a custom field on each Jira Issue so that some continuity of task momentum data is preserved. We flag the Hill Chart visualization gap in the migration report and recommend the Jira Sprint Progress gadget or a third-party burndown plugin as the replacement visualization.

Files attached to To-dos, Messages, or Documents in Basecamp migrate as Jira Attachments on the corresponding Issue or Project. We download each file from Basecamp's download URL, verify the file type and size, and upload it to the mapped Jira Issue. Attachments larger than 100 MB are flagged for chunked upload handling. Jira's attachment size limit (10 MB on Free plan; 50 MB on Standard and above) must be verified against the destination plan before migration begins. If the Basecamp attachment is an image embedded in a Document, it is downloaded separately and re-attached to the Document record or the corresponding Jira Issue.

Basecamp Comments attach to To-dos, Messages, and Documents with a body, author, and timestamp. We map them to Jira Issue Comments on the corresponding parent Issue. The comment body preserves plain text; markdown formatting is converted to plain text or Jira-compatible markdown. Author is resolved by email against the Jira destination User list. Comments on completed To-dos are attached to the same Jira Issue as the To-do itself, preserving the context regardless of completion state.

Basecamp Documents are rich-text pages created in Workdocs with a title, full HTML content, author, and creation timestamp. We export the full HTML content, download embedded images, and create a Jira Project-level attachment with the document as a PDF or HTML file. If the customer has a Confluence space linked to the Jira project, we migrate Documents to Confluence pages instead and link them from the Jira project description. The document title becomes the page title; author and creation timestamp are stored as page metadata.

Basecamp user roles within each project (Owner, Member, Guest) map to Jira project roles (Administrator, Member, Viewer). We extract the user list by email address and look up or provision matching Jira users in the destination. Basecamp Guests (clients, contractors) who do not count toward billing map to Jira users with Project角色 of Viewer or Contributor depending on the collaboration level needed. Users without Jira accounts go to a reconciliation queue for the customer's admin to provision before membership migration begins.