Google Calendar Import Missing Guests or Meeting Links?

Google Calendar's file importer does not import an event's guests or conference data. If the source ICS contains attendees but the imported event does not, that can be an expected limitation of the import route rather than a broken file (Google import instructions, checked November 5, 2026).

A meeting URL inside DESCRIPTION or LOCATION is a separate question. A surviving text link does not mean the event's structured conference data or invitation workflow transferred.

Key Takeaways

• Check the original ICS before deciding whether information was lost during import.
• ATTENDEE, ORGANIZER, and a URL in the notes describe different things.
• Repairing a file cannot make Google's importer preserve unsupported data.
• Recreating a live meeting requires an organizer decision, not just another file import.

Separate missing source data from an import limitation

Make a copy of the original export and search for the event's UID or distinctive title. Read the complete event, including folded continuation lines.

Use this field checklist:

| Information you need | Where to inspect | What its presence establishes | | --- | --- | --- | | Invitees | ATTENDEE properties | The export includes attendee records | | Organizer | ORGANIZER | The export identifies a calendar organizer | | Link in notes | DESCRIPTION | The URL exists as part of a text description | | Link in the place field | LOCATION | The URL exists as location text | | Event-related URL | URL | The event includes a URI property | | Conferencing metadata | Provider-specific properties or conferencing fields | The export carries additional data requiring provider interpretation |

The field definitions come from RFC 5545's event properties. The checklist is a way to inspect evidence, not a promise that Google preserves each property.

If the source has no attendees, changing its syntax cannot reconstruct the guest list. Check the original live event or request an export that includes the required information.

Read an attendee and text-link example

This synthetic calendar includes one guest and a URL in the notes. The example addresses and meeting URL are fictional. Save a copied file as UTF-8 with CRLF line endings.

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//CalendarLint//Guest Inspection Example//EN
BEGIN:VEVENT
UID:guest-inspection@example.test
DTSTAMP:20261105T000000Z
DTSTART:20261112T150000Z
DTEND:20261112T153000Z
SUMMARY:Migration planning
ORGANIZER;CN=Taylor:mailto:taylor@example.test
ATTENDEE;CN=Alex;PARTSTAT=NEEDS-ACTION:mailto:alex@example.test
DESCRIPTION:Join using https://meet.example.test/room-a
LOCATION:Online
END:VEVENT
END:VCALENDAR

The file contains an organizer, an attendee whose participation status is NEEDS-ACTION, and a plain-text meeting URL. It contains no provider-specific structured conference object.

That distinction matters when comparing an imported copy. A URL in the description is not equivalent to a functioning conferencing button, meeting ownership, or the ability to manage participants.

This file also has no METHOD:REQUEST. Treat it as an inspection example, not a procedure for sending a meeting invitation.

Compare the original with a temporary import

If you need to establish what happened to your file, use a temporary calendar and fictional participants. Record the source fields before importing, then inspect the resulting event.

| Item to record | Source example | Destination observation to collect | | --- | --- | --- | | Title and scheduled time | Migration planning, 15:00 UTC | Are the title and instant correct? | | Guest list | One ATTENDEE | Is a guest list shown? | | Organizer | Taylor's fictional address | Which organizer or owner does the destination show? | | Description | Contains a text URL | Is the complete text present? | | Conference controls | No structured conference in this sample | What does the actual migrated event provide? |

For Google's file importer, missing guests and conference data are documented behavior. The other cells require observation of your actual file and account. Do not infer that every Zoom or Teams URL disappears, or that a visible URL proves the original meeting is fully operational.

CalendarLint can help you inspect the exported event, including source properties and attendee details. It can establish what the file contains; it cannot establish that a provider will honor the old conferencing permissions.

Decide whether you need an archive or a live meeting

For a personal archive, retaining the title, dates, and readable notes may be enough. Keep the source export as the record of fields that did not transfer.

For a meeting that must continue to accept responses and updates, ask the original organizer or calendar administrator to choose the migration route. Check their provider's supported process for the specific account type and required fields. An ICS file import is not a complete invitation-state migration.

If an authorized organizer recreates a meeting, they should verify the guest list and create or confirm the conference through the destination provider. They also need to decide what happens to the old invitation. Otherwise participants can end up with two independent meetings.

Do not set PARTSTAT=ACCEPTED merely to imitate an old response, or replace ORGANIZER with your own address to try to acquire ownership. Editing those fields does not transfer the provider's permissions or create a response history.

Keep a field-by-field migration record

Before retiring the source calendar, retain a checklist for representative meetings: original identity, start and end, recurrence, guest list, organizer, URL location, and the destination's observed result.

Check exceptions in recurring meetings separately. A correctly imported master does not prove that a moved instance retains its meeting details.

If you need continuing updates, first distinguish importing from subscribing. Neither should be assumed to preserve a complete organizer-managed meeting lifecycle.

Verification scope: Google's current import documentation was checked November 5, 2026. The example's organizer, attendee, participation status, and description were parsed locally with ical.js 2.2.1. No invitations were sent and no Google import results are presented.