Bullet Journal Migration: How to Move Tasks Forward
Almost everything photographed about bullet journaling is decoration. The mechanic that actually decides whether the notebook is still open in November is the least photogenic one in the method: migration. At the end of a month you read every task you did not finish, and you copy some of them forward by hand.
Some. That word is the whole ritual.
What migration is
The bullet journal, the analog method created by Ryder Carroll, ends each month with a review of open items. You go back through the month's pages and look at every task still marked with a dot rather than crossed off. Each one gets one of four outcomes:
- Copied into the new monthly log, because you still intend to do it soon.
- Scheduled forward into a specific later month, because it has a real date and that date is not now.
- Moved to a collection, the page where that project or topic lives.
- Struck out. Not done, and not going to be.
A common convention marks a migrated task with a right-pointing arrow and a scheduled one with a left-pointing arrow, drawn over the original dot. That matters more than it looks. Months later, an old page tells you not only that a task existed but where it went, so nothing quietly disappears without a record of the decision.
The yearly migration is the same operation over a longer distance. When a notebook fills or a year turns, you set up the new book, then read the old one end to end and carry across only what is still alive.
Why it has to be by hand
Rewriting is slow, and the slowness is the mechanism.
A digital task list carries everything forward for free. Nothing costs anything to keep, so nothing gets removed, and after a year you have a list nobody can face reading. Paper charges a small toll. Copying a task takes eight seconds and, more to the point, eight seconds of attention aimed directly at that task. Somewhere around the fourth time you write call the insurance company in your own handwriting, you find out what you actually think about calling the insurance company.
This is not a productivity trick. It is closer to reading your own work aloud. The friction gives you a chance to notice something you have been avoiding noticing.
Running the monthly migration
Give it twenty to forty-five minutes, at a table, with the old pages and the new ones both open.
- Set up the new month first. Days down the left, the handful of things you already know have to happen. Do this before you look at last month, so you can see how much room there actually is.
- Read the whole month, not just the task lines. Front to back, dailies included. Half the value of the ritual is the reading.
- Decide each open task with a mark, not with a maybe. Arrow, arrow, collection, or strike.
- Migrate the notes too. A dash line worth keeping usually belongs in a collection, not in next month's log.
- Index anything new you created along the way.
If you finish and the new monthly log has thirty tasks in it, the migration did not happen. The list is a wish, and by the ninth item you will have stopped opening the book.
The honest question
For each open task, one question does most of the work:
Would I write this down today if it were not already written?
It is a zero-based test, and it is deliberately unkind to history. The task's age gives it no standing. The fact that you have carried it since March is not an argument for carrying it into April; if anything it is evidence against.
Two follow-ups, for the ones where the answer is unclear:
- Whose task is it? Some items are on the list because somebody once said something in a hallway and you wrote it down to be agreeable. It was never yours.
- What is the actual next action? If you cannot name a physical thing to do, it is not a task. It is a topic, or a worry. Rewrite it as a note and let it stop pretending.
Dropping is the work
Strike a dead task through with a single line. Do not erase it and do not tear the page out. A struck task stays legible, and legible is useful: at the end of the year you can see what you kept deciding not to do, which is a more honest portrait of your life than the finished column.
Some drops deserve a sentence. "Not doing this, the reason it was on the list stopped being true in June" takes ten seconds and saves you from writing the same task down again in October having forgotten you already settled it.
You will drop things that later turn out to matter. That is a real cost and it is smaller than the alternative, because a list you no longer open protects nothing.
We make Yesterself, a journaling app, and it does not do any of this. Task migration belongs on paper, where the rewriting costs you something. What the app does is the other side of the same instinct: any sentence you write can be postmarked to a future date and arrives on that day, and each morning it hands you back one letter drawn from your own past writing, with your evening reply becoming tomorrow's mail. It is not released yet, so there is nothing to download, only a waiting list.
Yesterself is the journal that writes back. Every morning it sends you a letter from your own past writing, and your reply becomes tomorrow's. End-to-end encrypted, no account, no email — your archive is yours to export, free, forever.
Join the waiting listThe yearly migration
The yearly pass, or the one that happens when a notebook runs out, works the same way but with more distance in it, and the distance changes what you notice.
Set up the new notebook first — page one, index, key — the way starting a bullet journal describes. Then read the old book straight through with a pen in hand. Carry forward the open tasks that survive the question. Copy across the collections you are still using, and only those. Anything with a date in the coming year goes into a future log, a page or two listing the months ahead so a dentist appointment in May has somewhere to sit.
Then write the old notebook's dates on its spine and keep it. It stays readable for decades and does not depend on a company still being in business.
When you have skipped it for months
Migration debt is the usual way the system dies. Three unmigrated months sit there, the job looks enormous, and the notebook stops being opened at all.
Do not pay the debt. Open the new month and write what genuinely matters now, from memory — the things that matter will come to mind unaided, which is itself a filter. Then make one quick pass over the old pages hunting only for items with dates attached, because those are the ones memory drops. Leave the rest where they are. Unmigrated pages are not a chain with a broken link in it. They are just pages from a month you were busy.
What a repeated migration is telling you
When the same task crosses three or four monthly boundaries in your own handwriting, stop treating it as a scheduling problem. It has told you something. There are three honest responses:
- Make it smaller. "Sort out the taxes" is not a task; "find last year's return" is.
- Give it a slot. Not a month — a day and an hour, written on the day.
- Drop it, with a line about why. This is the one people skip, and it is usually the right answer.
The notebook that lasts is not the neat one. It is the one that has been edited: pages with strikethroughs, arrows, and short notes about why a thing was let go. Migration is where the editing happens. Skip it and the book becomes an archive of intentions. Do it and it stays a record of decisions, which is the only version worth reading later.
Common questions
How often should I do a bullet journal migration?
Once at the end of each month, and once more when a notebook fills or a year ends. The monthly pass is short. The yearly one covers a whole notebook and takes longer.
Do I have to migrate every unfinished task?
No. Deciding what to drop is half the ritual. If a migration produces no strike-throughs at all, you transcribed the month instead of editing it.
What should I do with a task I have migrated four months in a row?
Treat the repetition as information rather than a failure. Either make the task smaller, give it a real date, or drop it and write one line about why it never moved.
How long does a monthly migration take?
Twenty to forty-five minutes for a normal month, most of it reading. A yearly or new-notebook migration usually takes a longer sitting, or two.
What if I skipped migration for three months?
Do not try to migrate three months in one go. Open the new month, write what actually matters now, then make one quick pass over the old pages looking only for things with dates attached.