Imports are reviewed before they change the current calendar. Use CSV to add a table of events, or a MonthSprig JSON file to restore an editable project. Keep the existing calendar in place while you inspect the file and resolve errors.
Prepare the file
For CSV, use UTF-8 text, one event per row and dates written as YYYY-MM-DD. The limit is 5 MB and 2,000 event rows. Include a header row that makes the columns recognizable. Save a smaller copy if the source spreadsheet contains unrelated tables or more events than you need.
A MonthSprig JSON project is different from event CSV. It contains the supported project structure, settings and events. Do not rename another file to .json to make it an importable project. Keep the original file until you have reviewed a successful restoration.
Match the CSV columns
Choose the file and map the columns to their calendar fields. Title and Start date are required. End date, Time label and Repeat are optional mappings. A column named Event name can map to Title; the name in your spreadsheet does not have to be identical.
Inspect the preview after mapping. Check a single-day event and a spanning event, and make sure each value landed in the intended field. An end date is the final included day. A time label is text, not a request for time-zone conversion. A monthly repeat uses the selected day number and skips months without it.
Correct or skip rows that need attention
An ambiguous date such as 03/04/2027 needs an explicit YYYY-MM-DD replacement. An impossible date such as 2027-02-29 must also be corrected. Read the original value and the error together so you can identify the intended date rather than guessing.
Review duplicate IDs separately from date errors. A duplicate may refer to an existing project event or to another row in the same file. Skip a row you do not want to add, or assign a distinct ID when it represents a different event. Resolving a duplicate should not silently overwrite an existing event.
Confirm only the changes you intend
Review the summary after the problematic rows are corrected or skipped. Check the number of ready events and the described effect on the current project. Confirm the import when that summary matches your intention. Until then, the existing events stay unchanged.
Use Back to mapping if a whole column was interpreted incorrectly, or discard the import if you chose the wrong file. A failed or cancelled import should not clear the calendar. If the file is large or unfamiliar, test a small set of representative rows before adding the full list.
Restore a JSON project safely
When importing a MonthSprig JSON file, review the project name, layout, date range and event count before confirming. A damaged file or unsupported version needs a clear error, not a partly restored calendar. Keep the current project available while you choose another file or recover a valid backup.
After a successful import or restoration, inspect the actual dates, longer spans and repeated occurrences. Save the result locally and download a fresh JSON backup if you want a separate copy. A readable preview is your chance to catch data that is valid in form but wrong for your intended calendar.