⚠️ Important
Legacy Calendar Sync has been deprecated.
This article applies only to Calendar Autopilot, the supported calendar synchronization solution for ExtendSync Google.
Calendar Autopilot reliably syncs most events between Google Calendar and NetSuite in real time.
However, some event types behave differently due to NetSuite platform limitations or time zone differences.
This guide explains those scenarios and what to expect.While most events sync accurately between NetSuite and Google Calendar, certain scenarios are affected by platform limitations, primarily within NetSuite. This guide explains those exceptions and what to expect.
Most Common Limitations
Multi-day Google events are split into one NetSuite event per day
Monthly recurring events after the 28th do not sync
Some monthly “day-of-week” recurrences won’t sync across time zones
Private Google events do not sync to NetSuite
Attendees without email addresses will not sync
Editing certain synced recurring events in NetSuite can create duplicates
Multi-day events (Resolved. Supported for Calendar Autopilot)
Multi-day events (Resolved. Supported for Calendar Autopilot)
Multi-day events spanning across several days
Action: Create
Scenario: Event created in Google over a period of several days
ExtendSync Calendar Sync Behavior
NetSuite does not support true multi-day events.
When a multi-day event is created in Google Calendar:
Calendar Autopilot splits it into multiple NetSuite events
Each NetSuite event represents one day of the original event
Editing a Multi-day event in NetSuite
Action: Edit
Scenario: User tries to edit one of the multiple events in NetSuite synced from a multi-day event in Google
ExtendSync Calendar Sync Behavior
Editing any of the split NetSuite events is not supported
An error will be displayed if attempted
Deleting of Multi-day event in NetSuite
Action: Delete
Scenario: Any one of the multiple events in NetSuite synced from a multi-day event in Google is deleted
ExtendSync Calendar Sync Behavior
Deleting any one of the split NetSuite events will:
Delete all related NetSuite events
Delete the original Google Calendar event
Multi-day event sync for different time zones
Action: Create
Scenario: Time zone difference exists between NetSuite Company and Google User Calendar. Event is created in Google Calendar spanning over multiple days
ExtendSync Calendar Sync Behavior
When the Google user time zone differs from the NetSuite company time zone:
Events are split based on the NetSuite company time zone
Times are then converted to the NetSuite user’s calendar time zone
📝 Important note
In rare cases, NetSuite may show an event where the end time appears earlier than the start time.
This is a NetSuite limitation. Interpret the end time as occurring the following day
.
Best practice
Create and manage multi-day events in Google Calendar, not NetSuite
Example:
Google Calendar Timezone: PST
NetSuite Company Timezone: CST
NetSuite User Timezone: PST
An event is created in Google as follows:
Start Time: 11/24/2013 8 am
End Time: 11/26/2013 8 am
The event is created as below in NetSuite:
Event 1 of 4: Date 11/24/2013 Start Time: 8 am End Time: 1:59 am
Event 2 of 4: Date 11/25/2013 Start Time: 2 am End Time: 1:59 am
Event 3 of 4: Date 11/26/2013 Start Time: 2 am End Time: 8.00 am
Recurring Events (Resolved. Supported for Calendar Autopilot)
Recurring Events (Resolved. Supported for Calendar Autopilot)
Recurring events created on day of week with a timezone difference
Case: Recurring events
Action: Create
Scenario: Recurring Events created as follows in Google Calendar: Select Repeat, Monthly, day of the week AND there is a timezone difference between the Google Calendar and NetSuite Company
ExtendSync Calendar Sync Behavior
Recurring events will sync only if the weekday remains the same after converting to the NetSuite company time zone. The day of week condition remain NetSuite same for all events in the destination recurring series. All other cases of recurring events are synced accurately.
If the weekday changes (for example, Thursday → Friday), the recurring series will not sync.
Example: “Last Thursday of every month”
Unlike Google Events which can be specified in different timezones on one calendar, NetSuite allows the creation of events only in the timezone of the user’s Calendar
Google Calendar Timezone: PDT
NetSuite Company Timezone: IST
An event is created in Google as follows:
Start Time: 10/31/2013 4 pm PDT (Thursday)
Repeat Monthly By Day of The Week (Last Thursday of Month)
Converting to the destination timezone of IST this event series looks like:
Source Series Event 1: Oct 31st at 4 pm PDT (Last Thursday of Month)
Source Series Event 2: Nov 28th at 4 pm PDT (Last Thursday of Month)
Destination Series Event 1: Nov 1st at 4:30 am IST (First Friday of Month)
Destination Series Event 2: Nov 29th at 4:30 am IST(Last Thursday of Month)
In the above case, it is not possible to replicate the source series into destination consistently, and hence the sync will not happen.
However, in a case such as below, the sync will occur seamlessly:
Google Calendar Timezone: PDT
NetSuite Company Timezone: IST
An event is created in Google as follows:
Start Time: 10/21/2013 2 am PDT (Monday)
Repeat Monthly By Day of The Week (Third Monday of Month)
Source Series Event 1: Oct 21st at 2 am PDT (Third Monday of Month)
Destination Series Event 1: Oct 21st at 2:30 pm IST (Third Monday of Month)
Source Series Event 2: Nov 18th at 2 am PDT (Third Monday of Month)
Destination Series Event 2: Nov 18th at 2:30 pm IST(Third Monday of Month)
Recurring events created in Google after the 28th of a month
Case: Recurring events
Action: Create
Scenario: Recurring Events created in Google Calendar: Select Repeat, Monthly, day of month after the 28th.
ExtendSync Calendar Sync Behavior
Recurring events scheduled on the 29th, 30th, or 31st will not sync.
Why
NetSuite does not allow monthly recurring events beyond the 28th.
Best practice
Use:
Weekly recurrences, or
Monthly recurrences on dates ≤ 28
Recurring events created in NetSuite of all types
Case: Recurring events
Action: Create
Scenario: Recurring Events of all types created in NetSuite regardless of the existence of a timezone difference between the two calendars
ExtendSync Calendar Sync Behavior
All recurring events created in NetSuite do sync to Google Calendar
Events are created using the originating event’s time zone
Recurring Event synced from GCal and Edited in NetSuite
ExtendSync Calendar Sync Behavior
Updating the start or end date of a synced recurring event in NetSuite:
Creates a new recurring series
Leaves the original series unchanged
Calendar Autopilot does not reconcile these two series.
Best practice
Edit recurring events in Google Calendar, not NetSuite
Time zone Behavior
Time zone Behavior
Company time zone changes after sync
Case: Recurring events
Action: Create
Scenario: Events created on a weekly recurring basis in Google Calendar and the timezone of the NetSuite company is changed after the event is synced to NetSuite
ExtendSync Calendar Sync Behavior
If the NetSuite company time zone is changed after recurring events are synced:
NetSuite cannot accurately adjust event times
This is a NetSuite platform limitation.
All-day events with time zone differences
Case: All-day events
Action: Create
Scenario: Create an All day event in Google or NetSuite. There is a timezone difference between the two Calendars.
ExtendSync Calendar Sync Behavior
All-day events remain on the same calendar date in both systems
📝 Reminder
NetSuite represents all-day events as 8:00 AM – 6:00 PM, not a true 24-hour span.
Privacy & Visibility Setting
Privacy & Visibility Setting
Google → NetSuite
Case: All events
Action: Create
Scenario: Events with Privacy Setting: Default/Public
ExtendSync Calendar Sync Behavior
Public / Default Google events → Imported as Public in NetSuite
Private Google events → Show as Busy
NetSuite → Google
Case: All events
Action: Create
Scenario: Private and Show me as Busy events created in NetSuite
ExtendSync Calendar Sync Behavior
Private or Show as Busy NetSuite events → Synced as Private to Google Calendar
Preferred form for imports into NetSuite
Preferred form for imports into NetSuite
Case: All events
Action: Any action
Scenario: Event created/updated in Google. A preferred form is set for Imports in the Calendar wizard for CloudExtend Setup.
ExtendSync Calendar Sync Behavior
Calendar events are created using the default form
Preferred form validation is not applied on creation
If edited later in NetSuite, preferred form validation will apply
This is a NetSuite calendar limitation.
Event created by an external person
Event created by an external person
Case: All events
Action: Create
Scenario: An event is created in Google by an organizer who has a different domain than the licensed domain. The said event has attendees on the event who are from the licensed domain.
ExtendSync Calendar Sync Behavior
Event syncs to NetSuite
Organizer is not synced
One licensed attendee is assigned as organizer in NetSuite
Updates made in NetSuite do not sync back to Google
Updates made in Google do sync to NetSuite
NetSuite events with attendees without an email
NetSuite events with attendees without an email
Case: Events with attendees without an email.
Action: Create/Edit
Scenario: When an event is created in NetSuite with attendees missing an email.
ExtendSync Calendar Sync Behavior
Events sync to Google
Attendees without email addresses are not synced
If edited in Google, those attendees are removed from NetSuite
🚨 Advice
Do not edit events in Google Calendar if they include NetSuite attendees without email addresses.
Best Practices
Prefer Calendar Autopilot for real-time accuracy and support.
Avoid monthly recurrences after the 28th.
Standardize time zones where possible.
Use Public visibility for events that must sync from Google to NetSuite.
Avoid editing split multi-day events in NetSuite.
Ensure all attendees have valid email addresses.
Need Help?
🔎 Search support.cloudextend.io
💬 Chat with Support (bottom-right widget)
📧 Email cloudextend-support@celigo.com
We’re happy to help you navigate Calendar Autopilot behaviors and ensure reliable event syncing.