Legacy calendar migration check record
======================================

Yenra | https://yenra.com/meeting-maker-millennium/
Updated September 16, 2026

How to use: Copy this plain-text worksheet into your editor and fill in the fields. Keep the source link and record your own assumptions and results.

Purpose: Plan an authorized migration or archive from an identified legacy Meeting Maker installation. This is not a converter or a version-compatibility guarantee.
Source client/server versions and operating systems:
Owner / access controls / connected servers:
Source copy location, creation method and date:
Export type and exact supporting documentation:
Destination / documented importer / notification behavior:
Outcome: readable archive or operational future scheduling?
Identity and resource mapping:
Sample: single event, all-day, recurrence, changed/canceled occurrence, timezone transition, attendees, room, private entry, delegation.
For each: source expected values / destination observed values / difference / owner:
Repeat-import behavior and duplicate prevention:
Unresolved omissions and acceptance decision:
Final export point / transition changes / rollback condition:
Retention and source-copy owner:
Source context: Oracle 10g and Lewis & Clark 2012 instructions are historical, version-specific examples. RFC 5545 defines iCalendar; actual transfer behavior depends on the exporter and importer.