Skip to main content

Calendar Autopilot: How Fields Are Mapped Between NetSuite and Google Calendar

ExtendSync Google | Calendar Autopilot field mapping reference

Updated today

⚠️ Important
Legacy Calendar Sync has been deprecated.
This article applies only to Calendar Autopilot, the supported calendar sync solution for ExtendSync Google.

When events sync between NetSuite and Google Calendar, Calendar Autopilot maps event fields between the two systems to ensure consistency and visibility across platforms.

This guide explains how those fields are mapped and how special cases (attendees, all-day events, and availability) are handled.


Core Field Mapping

The table below shows how NetSuite event fields map to Google Calendar fields during sync.

NetSuite Event Field

Google Event Field

Title

What

Location

Where

Date, From and To

When

Message

Description

Owner

Calendar

Recurrence Pattern

Repeats Pattern

Event Access

Privacy

Attendees

Guests/Participants


Attendee Mapping Behavior

Calendar Autopilot syncs attendees between NetSuite and Google Calendar using email addresses as the matching key.

NetSuite → Google Calendar

  • Go to the NetSuite record, create events from Communication > Activities > New Event

  • NetSuite attendees are mapped to Google Calendar participants.

  • The email address of the NetSuite attendee is used when creating the Google participant.

Google Calendar → NetSuite

  • Google Calendar participant emails are used to search for a matching NetSuite record.

  • Matching follows this order of precedence:

    1. Employee

    2. Contact

    3. Customer

    4. Vendor

    5. Lead

    6. Prospect

    7. Partner

    8. Job

If a matching NetSuite record is found, the attendee is added.
If no match is found, the attendee is not added to the NetSuite event.

💡 This ensures that only valid NetSuite entities appear as attendees.


All-Day Events & Availability (Free/Busy)

NetSuite and Google Calendar handle all-day events and availability differently. Calendar Autopilot bridges these differences as follows.

Key Platform Differences

  • NetSuite does not support true all-day events. By default, they are set up to cover a full business day from 8 am to 6 pm.

  • NetSuite also does not have an explicit Free/Busy state — events that reserve time are considered Busy by default.

  • The only way to avoid blocking time in NetSuite is to create a Private event.

The following table shows how CloudExtend handles these discrepancies when syncing events:

NetSuite

Reserve Time

NetSuite

All-day

Google

Busy/Free

Google

All-day

Yes

Yes

Busy

Yes

Yes

No

Busy

No

No

No

Free

Yes


📝 Important Notes

  • When an event is marked as All-Day in Google Calendar, the corresponding NetSuite event is created from:
    08:00 AM to 06:00 PM

  • This is because NetSuite does not allow events that truly span an entire day.

  • All NetSuite events that reserve time are treated as Busy in Google Calendar.

💡 To avoid blocking availability in NetSuite, create the event as Private.


Need Help?

If events or fields don’t appear as expected:

We’re happy to help you understand and optimize Calendar Autopilot syncing with ExtendSync Google.

Did this answer your question?