CORE CONCEPTS

Migration

Postponing an event should not erase the fact that it was once planned for today.

What migration means

In bullet journaling, migration is not just copying an unfinished item — it is a moment of re-deciding.

Does this still matter?
Will I do it another day?
Is it no longer needed?

Moving vs. postponing

In a normal calendar, changing an event’s date can erase when it was first planned. Velprium’s Postpone keeps the original and creates a follow-up.

July 17   Write launch post
             │  Postponed
             ▼
July 18   Write launch post
          └─ linked to the July 17 event

Preserving history

When the original is preserved, you can see:

The date first planned
How many times it was postponed
Activities that keep getting pushed

This is not a record of failure — it is data for understanding the gap between plan and reality.

Event relationships

Product note

The original and follow-up are separate Events but hold a relationship. Velprium records “migrated to” and “migrated from” links, so you can trace how many times an event was carried forward.

The migration flow

Select an Event
Choose Postpone
Pick the new date
A follow-up Event is created
The relationship is shown between the two

Migration is not task completion

Any Event can be postponed.
Meetings, work, exercise, and notes can all have a follow-up.
Even without a “done” state, the relationship in time is recorded.

Example use cases

Carry unfinished work to a follow-up tomorrow
Create a follow-up meeting next week
Spot frequently postponed Events in a weekly review

Related concepts