Changing a calendar-blocking system can alter more than visible appointments. Recurring rules, time zones, reminders, meeting links, privacy, resource calendars, shared access, task links, and automatic focus-time rules may behave differently after export or import. Evidence should prove that the new workflow protects important commitments and should make gaps visible before the old system is removed.
Define what is changing
Record the source calendar, destination calendar, account owner, affected people, migration window, and whether the change is a one-time move, a continuing subscription, or a change in the tool that creates blocks. List primary calendars, secondary calendars, shared calendars, resource calendars, birthday or holiday feeds, tasks, and external subscriptions separately. State which are included and why anything is excluded.
Create a baseline covering event count by calendar and date range, recurring series, exceptions, all-day events, time zones, private events, attachments, conferencing links, attendees, organizer status, reminders, free/busy visibility, color or category meaning, and automation rules. Use invented events for risky testing rather than altering live commitments.
Preserve export evidence
Google's calendar export instructions document exporting all calendars in an archive or an individual calendar as an ICS file from a computer. The guidance also notes that permission or administrator controls can prevent an export. Keep the export request time, account, selected calendar, date range if applicable, archive filename, file size, and a secure hash where useful.
Microsoft's Outlook calendar export guidance documents saving an ICS file and choosing the exported date range and detail. It also explains that an imported file is a snapshot, not an automatically synchronized calendar. Therefore record whether the new system received an imported snapshot, subscribed to a feed, or connected through a live account integration. These states are not interchangeable.
Build a representative test set
Before cutover, create harmless events that exercise the formats the real calendar uses: a single timed event, all-day event, recurring series, edited occurrence, cancelled occurrence, event spanning a daylight-saving change, event created in another time zone, private event, multiple reminders, attendee update, conferencing link, attachment, and resource booking. Include overlapping focus blocks and an event created by an automation.
After import or connection, compare title, description, start and end, time zone, recurrence rule, exception dates, attendee and organizer roles, response state, location, link, privacy, reminders, and availability. Do not use visual similarity as the only test. Open the event details and verify what recipients or collaborators can actually see.
Verify blocking behavior, not just events
Calendar blocking tools often calculate availability, protect focus time, move flexible blocks, or resolve conflicts. Record the rules before the change: working hours, buffers, minimum duration, priority, movable windows, weekends, travel, double-booking policy, and treatment of tentative or all-day events. Run the same invented week in both systems and compare results.
Test conflict creation, late meeting acceptance, deleted source events, offline edits, time-zone travel, daylight-saving transitions, and a disconnected integration. Record whether the system warns, silently moves work, duplicates blocks, or loses changes. If outcomes differ by design, document the accepted rule rather than forcing superficial equality.
Protect privacy and shared access
Map each calendar's owner, editors, viewers, free/busy viewers, public state, external guests, groups, and resource permissions. Verify them from a test viewer account. A private title should not become visible because an imported calendar received a broader default permission. Conversely, a team that depends on free/busy access should not lose it without notice.
Keep meeting descriptions, attendee lists, attachments, and exported ICS files in an approved location. Calendar exports may contain sensitive personal or business context even when they contain no document bodies. Do not include account credentials or recovery codes in the change record.
Keep cutover, rollback, and acceptance records
Record the final sync or export boundary, freeze period, changes made after that boundary, import logs, warnings, rejected events, duplicate handling, permission verification, and user acceptance. State how long the source remains available, who can reactivate it, and how new events would be reconciled during rollback.
The final packet should include the baseline, export files and hashes where appropriate, test matrix, field comparisons, recurrence and time-zone results, automation-rule comparison, permission map, exception list, cutover decision, rollback plan, and owner acceptance. Mark untested calendar types and unavailable administrator settings plainly. The evidence should let a later reviewer tell whether commitments were preserved, which behaviors intentionally changed, and whether the old calendar can be retired safely.
Sources
- Export events from your Google Calendar — Google Calendar Help
- Export an Outlook calendar to Google Calendar — Microsoft Support