Google Calendar: "Processed zero events"

Google Calendar shows this when an import added no events. Its help page gives two cases. Either the file was the .zip from Export, which holds one .ics per calendar and has to be opened first, or Import was clicked again after the first click had worked. If what you want from that export is hours per client, ClientHours reads the .zip as it downloaded, with every calendar inside, and puts nothing into Google.

What Google Calendar's help page says

You'll see ICAL files (ending in “ics”) for each of your calendars.

You'll need to import each file that ends in “ics” individually.

You can also get the "Processed zero events" error if you clicked the Import button more than once.

Quoted word for word from Google Calendar's help page, listed under Sources.

Why it happens

  • The file picked in Import calendars was the .zip that Settings, Import & export, Export downloads. Google's page asks for the .ics files inside it, one at a time.
  • Import was clicked twice. The first click brought the events in, so the second click had no new events to process.
  • The .ics or CSV file is not formatted the way Google expects. Google's page sends you to check the formatting if the events are still missing after the steps above.

How to fix it

  1. Look in the calendar first. If the events are there, the first import worked and you are done.
  2. Find the .zip on your computer and double-click it. You get one .ics file for each of your calendars.
  3. In Google Calendar, click Settings in the top right and then Settings, open the Calendars tab and click Import calendars.
  4. Choose one .ics file and the calendar it should go into. Events land in your main calendar unless you pick another. Repeat for every .ics file.
  5. If you only need the hours, drop the unopened .zip on the ClientHours Google Calendar page and pick your dates.

Google Calendar to timesheet by client

What ClientHours does with the file

  • The .zip is unpacked in your browser. Every .ics file inside is read, and Your files lists each by name with the .zip it came from and its number of event records.
  • A meeting found in two calendars of the same .zip, with the same event ID and start, counts once. The page says how many it counted once.
  • The time zone of the timesheet starts as the one the file names, when your browser knows that zone.
  • A test .zip with two calendars and three events, run through the engine on 2026-11-18, gave three rows and 4.5 hours split across two clients.

Limits

  • ClientHours makes timesheets and import files for time trackers. It does not put events back into Google Calendar or any other calendar.
  • Files in the .zip that do not end in .ics, .ical, .ifb or .csv are skipped. An encrypted .zip is refused with a message, and the contents may unpack to at most 200 MB.
  • ClientHours has not yet been run on a real Google Calendar export. Its test calendars are built by hand from the iCalendar standard and Google's help pages, so check the first timesheet against your calendar.

Questions

Do I have to unzip the Google export?
For Google Calendar's own import, yes. Its help page says to open the .zip and import each .ics file on its own. ClientHours takes the .zip as it is.
Why did my second import say zero events?
Google's page says the first click imported the file, so the second found no new events to process. Check the calendar before you import again.
Can one export hold several calendars?
Yes. Export under Import & export downloads one .zip with an .ics file for each of your calendars. ClientHours reads them in one go and adds them to one timesheet.

Sources

Other import problems

ClientHours is free, with no account and no payment. The calendar file never leaves your browser.