How to Switch Student Planners Mid-Semester Without Losing Deadlines

To switch student planners mid-semester, move the work you still owe, verify it against current course sources and choose a clear point when the new planner becomes your working list. Keep the old one as a reference until the replacement is complete. Copying every entry is not the same as checking every obligation.

The procedure below works whether you are moving from paper, a spreadsheet, Notion or another app. It is a manual reconciliation method, not a claim that one tool can automatically import another's data.

Decide whether switching solves the actual problem

Name the failure before moving anything. “I cannot see deadlines across courses” is specific. “I need a nicer dashboard” does not tell you which part of your system will improve.

A switch is more defensible when the new tool handles a recurring requirement you cannot reliably manage now: finding outstanding work, separating courses, correcting dates or reducing repeated syllabus entry. If you mainly need to check the current planner regularly, importing the same list elsewhere may leave that problem intact.

Choose a time when you can finish checking the migration. During an immediate deadline emergency, complete the urgent task first and record anything missing in a temporary note. Do not retire a functioning planner halfway through transferring it.

Preserve a reference copy before editing

Use the old tool's supported export or keep a private, readable copy of the relevant records. Check that you can actually open the copy and see task names, course labels, dates and completion status. A file that downloaded successfully may still omit the fields you need.

For example, Notion's export documentation describes HTML and Markdown/CSV exports. Such an export can serve as a reference during migration; it is not evidence that the destination accepts that format or reconstructs your database behavior.

Keep the official syllabus, assignment pages and instructor changes available too. The old planner might contain a stale deadline, an omitted task or your personal work target instead of the official due date.

Handle these copies privately. Before uploading a syllabus to a new service, check course permission and the service's current privacy terms. UBC's student guidance on generative AI specifically cautions against uploading instructor-created materials without permission. Your own institution's rules govern your situation.

Sort the old records into four groups

Do this course by course rather than relying only on a chronological calendar view.

“Overdue” does not automatically mean “finished” or “still recoverable.” Check the course policy and current status. Likewise, a submitted proposal and a future final paper may be separate requirements, even when their titles are similar.

Keep administrative actions that still matter, such as a booking or an instructor follow-up, but distinguish them from assessed assignments. A migration should not silently erase an obligation just because it does not fit the new tool's default category.

Build a course-by-course reconciliation list

For each outstanding item, compare three things: the current course source, the old planner and the new planner. The current source decides what needs correcting; the old planner is supporting evidence, not the authority.

Use a temporary checklist with these fields:

• Course and exact task name.
• Official due date and time, or the unresolved state.
• Current status and any remaining action.
• Source last checked.
• New record verified: yes, no or needs clarification.

Keep the checklist outside the app if it does not support these fields. It is a migration aid, not a required permanent dashboard.

For large assignments, preserve the distinction between the submission deadline and personal milestones. Moving “outline Tuesday” must not accidentally replace “final paper Friday.” If two entries appear identical, use the assignment duplicate checks before deleting one.

Worked example: moving three courses in October

This is an illustrative migration, not a real student's record or an app benchmark.

The old planner contains 46 entries: 27 completed items, 17 dated outstanding items and two outstanding tasks marked TBD. The starting expectation is therefore 19 outstanding items, not 46 new deadlines. That count is a checkpoint, not proof of correctness.

During verification, the student finds these cases:

Suppose the new planner also ends with 19 outstanding items. That still does not establish a successful move: one missing task and one duplicate would cancel out numerically. Check identity, date and status, not just totals.

If you are moving into Qumely

Qumely's syllabus upload accepts PDF and Word (.docx) syllabi, extracts details for review and lets you correct them before explicitly confirming them into Qumely's calendar. Treat that as a starting point for the course reconciliation.

A syllabus may predate instructor changes or omit assignments added later. Compare the reviewed result with current course information and your outstanding-work list. Check the confirmed course and tasks before treating the move as complete.

This is not a bulk migration from a Notion database, spreadsheet or ICS file. It does not establish automatic duplicate detection, a Canvas connection or Google/Apple calendar synchronization. If one of those is essential to your existing workflow, resolve that requirement before switching.

Set a cutover point and test the replacement

Choose a specific point after reconciliation when the new planner becomes the place you update. Keep the old copy clearly labelled as a reference so you do not continue maintaining two competing deadline lists.

Before retiring the old working system, find each of the following in the new one:

• The next deadline for every active course.
• A major assessment beyond the next week.
• Each unresolved date.
• Any overdue item that still requires action.
• A recently changed deadline and its corrected value.

After your first normal course-information check, confirm that changes can be recorded where you now expect to find them. If an item cannot be represented safely, keep it in a clearly identified exception note until you choose how to handle it. Do not bury that exception in an archive.

Stop maintaining the old planner only when you can answer: what is still owed, where is it recorded, and which source verified it? For the ongoing routine after the move, use one reliable assignment-tracking system.