Migrate your DoneDone data
A lightweight issue tracker combining shared inbox and task management for small-to-mid software teams. Favors simplicity over configurability.
In its favor
Why people choose DoneDone
The signal that keeps DoneDone on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Small teams pick DoneDone because it requires almost no setup to start tracking issues — the free tier and built-in workflow templates get a project live in under an hour.
The combined shared inbox and task management model means support teams do not switch between a mailbox and a separate project tool to resolve a customer issue.
Built-in workflow templates for bug tracking, task tracking, and customer support come preconfigured with sensible status progressions and default assignments.
Integrations with GitHub, Harvest, Slack, and Google Drive cover the most common tooling stacks for development teams without requiring custom configuration.
DoneDone lacks the advanced reporting and analytics that growing teams need to demonstrate team velocity, SLA compliance, or trends over time, pushing them toward platforms with built-in dashboards.
The flexible project structure, while useful initially, can cause projects to diverge organically — teams find themselves with inconsistent workflows across projects as the team grows.
Scaling limitations become apparent for larger organizations: fewer administrative controls, no enterprise SSO options documented, and pricing per-seat that grows unfavorably against platforms with volume discounts.
Custom automation capabilities are limited compared to modern helpdesk tools — teams that rely on complex routing, SLAs, or auto-escalation find DoneDone cannot support those workflows.
Reasons to switch
Why people leave DoneDone
The recurring reasons buyers give for replacing DoneDone. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where DoneDone fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
DoneDone pricing overview
DoneDone uses a per-seat monthly subscription model at $5/user/month on the Standard plan, with a Free tier for single users and an Enterprise tier with custom pricing for larger organizations. No annual discount tiers are publicly documented.
Free
Tier 1 of 3
Free
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on DoneDone's schedule — see our quote-based pricing →
What gets migrated
DoneDone object support
Object-by-object support for DoneDone migrations. Per-pair details surface during scoping.
Issues
Fully supportedIssues are the primary record type in DoneDone. They carry title, description, status, priority, assignee, watchers, due date, linked tasks, attachments, tags, and a full edit history. We map all standard fields directly to the destination.
Projects
Fully supportedProjects group issues under a named Workflow. Projects themselves hold configuration including default fixer and tester roles, priority settings, and tag defaults. We preserve project hierarchy and settings 1:1.
Workflows
Fully supportedWorkflows define the ordered list of Statuses and which transitions are permitted between them. DoneDone ships built-in templates (Bug Tracking, Task Tracking, Customer Support, Hiring) and supports fully custom named workflows with colors. We copy workflow definitions and map status transitions to the destination's equivalent stages.
Statuses
Fully supportedStatuses are ordered steps within a Workflow, each with a name, color, and position index. We preserve the sequence and color but remap color assignments to the destination's palette.
Tags
Fully supportedTags are flat labels applied to Issues across Projects. DoneDone does not support tag hierarchy or tag categories. We migrate tags as a flat string array on each Issue record.
Saved Replies
Mapping requiredSaved Replies are template text snippets that agents use to respond quickly to recurring ticket types. The destination helpdesk may not have an equivalent Saved Replies concept — we flag this and offer to map them to canned responses or email templates as appropriate.
Assignees and Watchers
Mapping requiredDoneDone allows multiple watchers per Issue in addition to a primary assignee. Many destination platforms support only a single assigned user. We flatten to the primary assignee and preserve the full watcher list as a custom multi-select property.
Private Comments
Mapping requiredDoneDone supports private commenting on Issues — visible only to internal team members, not to the end customer. The destination platform may not have an equivalent internal-note concept, or it may conflate internal and public comments. We map private comments to the destination's internal note field and flag any visibility mismatches.
Linked Tasks
Mapping requiredIssues can reference other Issues as linked sub-tasks or related items. The relationship semantics (parent-child, blocks, relates-to) vary across platforms. We preserve the raw linked-issue IDs and apply a configurable mapping of relationship types at migration time.
Attachments
Mapping requiredAttachments on Issues include file name, size, uploader, and a URL pointing to Google Drive integration (the native file store). We download attachments and re-upload them to the destination's file store, preserving uploader metadata.
Task History
Fully supportedEvery Issue carries a timestamped history log of field changes (status, assignee, priority, description edits). We export this as a chronological array of change events and replay it as comments or a custom history object in the destination.
Reporting
Mapping requiredDoneDone exposes a Reports dashboard within the application. Reporting data is generated on-demand and is not stored as a separate data object. We cannot migrate historical reporting snapshots — we flag this gap and advise customers to export reports as PDFs before migration if retention is required.
| Object | Support | Notes |
|---|---|---|
| Issues | Fully supported | Issues are the primary record type in DoneDone. They carry title, description, status, priority, assignee, watchers, due date, linked tasks, attachments, tags, and a full edit history. We map all standard fields directly to the destination. |
| Projects | Fully supported | Projects group issues under a named Workflow. Projects themselves hold configuration including default fixer and tester roles, priority settings, and tag defaults. We preserve project hierarchy and settings 1:1. |
| Workflows | Fully supported | Workflows define the ordered list of Statuses and which transitions are permitted between them. DoneDone ships built-in templates (Bug Tracking, Task Tracking, Customer Support, Hiring) and supports fully custom named workflows with colors. We copy workflow definitions and map status transitions to the destination's equivalent stages. |
| Statuses | Fully supported | Statuses are ordered steps within a Workflow, each with a name, color, and position index. We preserve the sequence and color but remap color assignments to the destination's palette. |
| Tags | Fully supported | Tags are flat labels applied to Issues across Projects. DoneDone does not support tag hierarchy or tag categories. We migrate tags as a flat string array on each Issue record. |
| Saved Replies | Mapping required | Saved Replies are template text snippets that agents use to respond quickly to recurring ticket types. The destination helpdesk may not have an equivalent Saved Replies concept — we flag this and offer to map them to canned responses or email templates as appropriate. |
| Assignees and Watchers | Mapping required | DoneDone allows multiple watchers per Issue in addition to a primary assignee. Many destination platforms support only a single assigned user. We flatten to the primary assignee and preserve the full watcher list as a custom multi-select property. |
| Private Comments | Mapping required | DoneDone supports private commenting on Issues — visible only to internal team members, not to the end customer. The destination platform may not have an equivalent internal-note concept, or it may conflate internal and public comments. We map private comments to the destination's internal note field and flag any visibility mismatches. |
| Linked Tasks | Mapping required | Issues can reference other Issues as linked sub-tasks or related items. The relationship semantics (parent-child, blocks, relates-to) vary across platforms. We preserve the raw linked-issue IDs and apply a configurable mapping of relationship types at migration time. |
| Attachments | Mapping required | Attachments on Issues include file name, size, uploader, and a URL pointing to Google Drive integration (the native file store). We download attachments and re-upload them to the destination's file store, preserving uploader metadata. |
| Task History | Fully supported | Every Issue carries a timestamped history log of field changes (status, assignee, priority, description edits). We export this as a chronological array of change events and replay it as comments or a custom history object in the destination. |
| Reporting | Mapping required | DoneDone exposes a Reports dashboard within the application. Reporting data is generated on-demand and is not stored as a separate data object. We cannot migrate historical reporting snapshots — we flag this gap and advise customers to export reports as PDFs before migration if retention is required. |
Gotchas
What to watch for in DoneDone migrations
Issues we've hit on past DoneDone migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Reporting data cannot be exported as structured records
Private comments require explicit visibility handling
Flexible project structure causes workflow divergence over time
Multi-watcher Issue model requires flattening for most destinations
API access is permission-gated to match application access
| Severity | Issue |
|---|---|
| High | Reporting data cannot be exported as structured records |
| High | Private comments require explicit visibility handling |
| Medium | Flexible project structure causes workflow divergence over time |
| Medium | Multi-watcher Issue model requires flattening for most destinations |
| Low | API access is permission-gated to match application access |
Leaving DoneDone?
Where DoneDone customers move next
7 destinations DoneDone can migrate to.
How a DoneDone migration works
Four steps, DoneDone-specific
Connect
API key (per-user, scoped to the authenticated user's permissions) into DoneDone. Scopes limited to read-only on the data we move.
Map
We translate DoneDone-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate DoneDone quirks before production.
Migrate
Full migration with DoneDone rate-limit handling. Rollback available throughout.
FAQ
DoneDone migration FAQ
Answers to the questions buyers ask most during DoneDone migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your DoneDone migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther helpdesks we support
Ready when you are
Migrate DoneDone.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your DoneDone setup and destination — written quote back within a business day.