Migrating via the install tool

The most obvious possibility to migrate entries will be the upgrade wizard within the Admin Tools => Upgrade Module in TYPO3 9LTS respectively in the install tool in TYPO8 LTS. You will find an additional Upgrade Wizard named "Migrate entries from ext:cal to calendar_foundation".

Migrating via the shell

The Upgrade Module is a valid way, if you have only a couple of entries (e.g. 200 or so). If you have huge databases or are a speedster, this extension offers also a CLI script "calendar:migrate". Using this script processes the entries much faster.

Warning: If you use one or more of the following features, the will not migrated during the upgrade. Therefore ensure to save a backup of the old cal data, because with new features we tend to improve the upgrade wizards accordingly to add your existing data to the calendar features.

Over the years, cal growed to a non maintainable feature loaden moloch. That, one the one hand is great, because you could use cal in a variaty of differenc scenarios. But, as written above, that was not maintainable and was the ultimate reason to rewrite cal from scratch. To keep the calendar framework maintainable, it was decided to split the core from all the nice little features and (maybe) provide tham later on in seperate extensions. So, for now, the calendar framwork lacks, not necessarily exclusively, the following features:

• Addresses: Currently there is no way to add addresses to calendar entries. Neiter in a text area nor as separate address entries. That also means, that no mapping of event loactions is possible.
• Organizers: The same goes for the organizers of calendar entries.
• Frontend editing: If your use case rely on frontend editing, the calendar framework currently offers no backup solution for you.
• iCal exports et al.: If you in dear need of such implementation, you might check how the Frontend Controller gains the data from the API and then just use any ical package.

During the migration no database entry of ext:cal is touched. In fact every migrated entry from ext:cal to calendar_framework will be enriched with the uid of the original ext:cal entry. So it should be easy to create an own extension to continue the work of this extension.