Migration

Move from Things 3 to Done Bear

Things 3 has no export menu, but its database is readable. Run one CLI command on a Mac or upload main.sqlite. Areas, projects and to-do dates come across.

Last updated 2026-09-27

Start your import Preview without an account

Free up to 250 tasks, completed tasks included. No credit card.

The short answer

Done Bear imports Things 3 from a copy of its local database, so areas, projects, headings, tags, checklists, dates and completed work arrive together. Run it from the CLI on the Mac where Things lives, or upload main.sqlite in the web import wizard. Nothing is ever written back to Things.

Key takeaways

Things 3 has no export command, so Done Bear reads a copy of its database.
Areas become teams and headings stay headings, so structure survives.
Today, Upcoming, Anytime and Someday keep their placement.
The importer is read-only against Things and can be undone afterwards.
One CLI command on the Mac does the whole import.

What to export from Things 3

The file to bring from Things 3: Things database file. These are the steps the import wizard shows, so the file you make is one it accepts.

1.On iPhone or iPad: Things → Settings → General → Diagnostics → Enter Code → 491348 → Send Things Database.
2.The file is Things Database.aar. Save it to Files. Tap it to unpack to Things Database.thingsdatabase, or import the .aar in the Done Bear iOS app.
3.On the web, choose main.sqlite from inside that bundle, or a zip of the folder. Web cannot unpack .aar yet.
4.On a Mac: in Finder, press ⇧⌘G and paste the folder path below. Do not type it: ~/Library is hidden.
5.Open the ThingsData-… folder inside it, then Things Database.thingsdatabase.
6.Copy main.sqlite to your Desktop. Copy it, do not move it, or Things loses its list.
7.Choose that copy here. The CLI (donebear import things) still finds the Mac database itself.

What Things 3 concepts become in Done Bear

This table is the whole mapping from Things 3 to Done Bear. Read the notes column before you import, because the exceptions are there.

Things 3	Done Bear	Notes
Area	Team	Every project filed under an area joins that team.
Project	Project	Notes, deadline and completion date come with it. The project arrives active: its own start date and Someday placement are dropped, and its to-dos keep their own lists.
Heading	Heading	Headings stay headings inside their project, so the task list keeps its sections.
Tag	Label	Tags on an area or project are added to each to-do inside it. The project itself carries none.
Checklist item	Checklist item	A title longer than 500 characters is truncated.
Today, Upcoming, Anytime, Someday	Today, Upcoming, Anytime and Someday	A Someday task stays in Someday. A scheduled task keeps its date and lands in Upcoming.
This Evening	Today	This Evening to-dos land in Today, without the evening split.
Deadline	Deadline	Deadlines are separate from start dates on both sides, so neither one overwrites the other.
Repeating to-do	Repeat rule	A rule Done Bear can run exactly is kept as one. A rule it can only approximate arrives narrowed, with a warning. A rule it cannot run is kept as text on the task, and no repeat is stored that would fire on the wrong days. A paused repeat stays paused. A repeat on a fixed schedule keeps its end date or count and stops where it would have in Things. A repeat set to run after completion comes across without its end, so it keeps going. The import preview names each one so you can stop it yourself.
Logbook	Logbook	Completed to-dos keep their completion dates, so finished work stays finished.
Canceled to-do	Trash	Canceled to-dos go to Trash, not the Logbook. Things’ own Trash goes to Trash too.
Notes	Description
Contact	Not imported	A contact on a to-do is dropped.

What comes across and what does not

Done Bear imports the fields below from Things 3. The second list is what stays behind, so you can decide what to save by hand before you delete anything.

Comes across

Areas and folders (become teams)
Completed tasks
Tags and labels
Projects and lists
Repeating tasks
Sub-tasks

Stays behind

Attachments
Reads a copy of the Things database; Things itself is never written to.
On the web, choose main.sqlite or a zip of a .thingsdatabase folder. Apple Archive (.aar) is unpacked in the Done Bear iOS app; tap the export on iPhone to unpack it first if you are importing here.

Running the import

The import wizard lives in Settings, Integrations & Import, Import from another app. Choose Things 3, upload your file, and Done Bear previews every record it found. Nothing is written until you confirm.

The CLI runs the same import from the terminal, and it finds the Things 3 database itself:

npm install -g donebear
donebear auth login
donebear import things --dry-run
donebear import things

Start your import

Re-running it and undoing it

Re-importing the same file is safe. Done Bear recognises the tasks it already brought across from that export and adds only what is new. The completion screen offers an undo, which removes what the import created and keeps anything you have edited since.

Read the import documentation

Frequently asked questions

Does Things 3 have an export button?

No. Things 3 ships no export command on any platform. What it has is a local database: a readable SQLite file inside the Things container on your Mac, and a Diagnostics code on iPhone and iPad that sends the same database as an archive. Done Bear reads a copy of that file.

Is it worth importing a small Things list?

Copy and paste is faster under a hundred active tasks. Things copies selected to-dos as plain text, one per line, so you can paste the list into Done Bear and retype what still matters. You lose dates, notes, area structure and the Logbook, which is often the point.

Should I import everything or start fresh?

Import, then delete in the new app. A database that is mostly archaeology still imports in one pass, and one pass through Someday afterwards clears it faster than deciding item by item beforehand. Deleting in an app you have no history with costs less.

Does the import change my Things database?

No. The importer opens a copy of the database read-only and never writes to Things, so both apps hold the same list until you decide. Keep Things installed for a month as a safety net while the new system earns your trust.

Can I import Things 3 from an iPhone?

Yes. In Things on iPhone or iPad, open Settings, General, Diagnostics, Enter Code, then 491348 and Send Things Database. The Done Bear iOS app imports the resulting Apple Archive directly. On the web, choose main.sqlite from inside the unpacked bundle instead, because the web uploader cannot unpack .aar yet.

Where this information comes from

Done Bear, Import from Things 3 (the Done Bear CLI imports Things 3 from the Mac database with dry-run, metadata and team flags)
Done Bear, Importing from another app (every import previews what it will create before writing, and undo keeps rows you have edited since)
Done Bear, Done Bear vs Things 3 (Things 3 is sold separately for Mac, iPhone, iPad and Vision Pro, with no web, Windows, Android or Linux version and no team workspaces)