Bullet journal migration: how to do it, daily and monthly
Migration is the habit that separates a bullet journal from a notebook full of old to-do lists. Once a day or once a month you go back over what is still open, and for each task you make a decision: carry it forward, move it somewhere else, or let it go. Everything else in the method (rapid logging, the monthly log, the future log) exists so that this review has something to work on.
This guide covers what migration is, how to run it at the daily and monthly level, the questions that make it quick, and how it works in a digital journal, where there is no pen to slow you down.
Daybook is a bullet journal for iPhone and Mac.
What migration actually is
In the Bullet Journal method, created by Ryder Carroll, an open task is marked with a dot (•). When you decide a task still matters but did not get done, you mark it with a right-pointing arrow (>) and write it again on a new page. The old page keeps the arrow, so it shows where the task went. Tasks that belong to a later month use a left-pointing arrow (<), meaning "scheduled": they go into the future log or a future monthly log.
The rewrite is not busywork. It is a deliberate pause: if a task is not worth writing again, it was probably not important, and you can cross it out. People who keep a bullet journal for years usually say this filter is the point of the system.
The four outcomes
Every open task ends up in one of four places:
- Today (or the current month). It is still relevant and you will work on it soon. Migrate it forward.
- A later date. It matters, but not now. Schedule it (<) into the future log or a future month, so it comes back when it should.
- A collection. It is not really a task for a day, it belongs to a project, a list or a theme (a trip, a house move, a reading list). Move it to a collection and stop carrying it day to day.
- Cancel. It no longer matters. Strike it through. This is a good outcome, not a failure.
Daily migration
At the end of the day (or the first minute of the next one), look back at today's page and ask of each task that is still open:
- Is it still relevant? If the reason for the task is gone, cancel it.
- Does it have to happen today or tomorrow? If so, migrate it to the next day.
- Does it have a real date? If it is tied to a day or month, schedule it there instead of dragging it along every day.
- Is it part of something bigger? Move it to the matching collection.
A task that gets migrated three or four days in a row is telling you something. Either it is too big (split it into a first physical step), it is not yours to do (cancel or delegate), or you do not actually want to do it (cancel, honestly). Spotting these is what a daily migration is for.
Monthly migration
On the last day of the month or the first day of the next one:
- Set up the new month first: the monthly calendar and a fresh task list.
- Go through last month's pages and collect every task still open, including the ones sitting on the monthly task list.
- Open the future log and pull in whatever now falls in this month.
- Decide each task, with the same questions as above: carry into the new month, schedule it later, move to a collection, or cancel.
The monthly pass takes longer than the daily one, which is fine. It is also where most of the clean-up happens, because months of open tasks get compared with what actually mattered.
Doing it on paper vs in an app
On paper the friction is the feature: you have to write each task again, so you only keep what you care about. The cost is time and the temptation to skip it on a tired evening.
An app removes the rewriting, which makes migration fast but also makes it easy to drag everything forward without thinking. A good digital journal should keep the decision and drop only the typing:
- It should gather every open task from earlier days in one place, so you do not hunt through pages.
- It should leave the original marked as migrated (>) or scheduled (<), the way paper does, so your history stays truthful.
- Moving a task should be one gesture or one key, with the destination (today, this month, a future date, a collection) offered right there.
Daybook is built around that. Its Migrate page lists every open task from earlier daily and monthly logs, grouped by the page it came from. You choose where each one goes: today, this month, a collection or a future date. The original stays on its day marked > (or < when you schedule it into a future month), and the copy at the destination says where it came from. On the Mac, ⇧⌘T migrates the focused task to today. On the 1st of the month it offers the month review, so the monthly pass actually happens.
A simple routine to start
- Two minutes at the end of the day: look at today, migrate or cancel what is open.
- Ten minutes on the 1st: set up the month, run the monthly pass.
- Once a month, count how many tasks you cancelled. If it is zero, you are probably carrying too much.
FAQ
FAQ
How often should I migrate in a bullet journal?
Daily for a short look at what is left open, and monthly for the full review. Many people also do a quick weekly glance, but the method itself only asks for daily and monthly.
What does the > symbol mean in a bullet journal?
It marks a task that was migrated: you decided it still matters and moved it to a new page, such as the next day or the next month. The arrow stays on the old page so you can see where it went. A < arrow marks a task that was scheduled into the future log.
Should I migrate every unfinished task?
No. Migration exists to force a decision. Tasks that are no longer relevant should be cancelled, and tasks that belong to a project should move to a collection instead of being carried day after day.
Does migration work in a digital bullet journal?
Yes, if the app keeps the decision and only removes the rewriting. Look for one view of all open tasks, clear migrated and scheduled markers on the original entry, and a quick way to choose the destination.
Keep reading
Daybook is a bullet journal for iPhone and Mac.
Last updated: 2026-11-09