An ICS file moves date-based events to a compatible calendar application. It does not connect MonthSprig to that application or keep the two calendars synchronized. Review the selected dates before exporting and inspect the result after importing.
Review the calendar range and events
Check the selected year or date range, event titles and any longer spans. Review repeated occurrences in the range you intend to move. A birthday layout without a printed year still needs a real year or date range for date-based ICS entries.
Optional time labels remain text. A label such as 14:30 does not define a time zone, duration or reminder. Do not use the file as evidence that a precisely timed appointment has been scheduled in another service; create or check that appointment’s time there if you need one.
Download the ICS file
Open the download options and choose ICS. Wait for the actual file to finish, then keep it in a location where you can find the version you intend to import. If the export fails, preserve the project and read the error before retrying.
Keep a JSON project backup as well. ICS contains calendar event information, not the complete MonthSprig editing state. It does not replace the file you need to restore the layout, colors and other project settings later.
Understand date-only values
All-day ICS entries use DATE values written as YYYYMMDD. A March 8, 2027 start can be represented as DTSTART;VALUE=DATE:20270308. A DATE value does not carry a time-zone identifier because it represents the chosen calendar date rather than a timed instant.
This distinction helps keep an all-day event on the intended day. You enter normal dates in MonthSprig; you do not need to type ICS properties into the event form. If you inspect a downloaded file, read the date values with that convention in mind.
Check the final day and repeated dates
The event form includes the end date you select. In ICS, DTEND is the first day after the event. A March 29–31 span uses DTSTART;VALUE=DATE:20270329 and DTEND;VALUE=DATE:20270401. It covers three days, not four.
Repeated dates follow the project’s explicit rule. A monthly day-31 event skips shorter months, and a yearly February 29 event skips non-leap years. Inspect expected occurrences around those boundaries. A missing nonexistent date is the intended skip behavior, not a reason to move the event silently.
Check the receiving application
Use the receiving calendar application’s import process, then inspect a single-day event, a spanning event and a repeated example. Check the first and last included dates and the event text. The application controls its display and how it handles importing the same file again.
Do not assume that a second import will replace the first without duplicates. Review that application’s behavior before moving a large set of events. Editing the MonthSprig project afterward does not update previously imported entries automatically. Export a fresh file when needed and keep clear versions of the source project and output.