To keep a phone and desktop calendar in step, add the same calendar account to both and create events in the intended calendar within that account. An imported file is a separate copy; a subscribed feed is usually a view of another publisher’s calendar. Those arrangements solve different problems.
Start by writing down the account address, calendar name, and app on each device. One app can display several calendars at once, which can make a local event or a subscribed copy look as if it belongs to your primary account.
Identify the connection
Scroll the table horizontally on a small screen. Keyboard users can focus the table region and use the arrow keys.
| Connection | How changes travel | Useful check |
|---|---|---|
| Same supported account on two devices | Account-backed changes synchronize according to the service and app. | Create and edit a test event from both ends. |
| Shared calendar with editing permission | Authorized members can change the shared calendar. | Check the permission and selected calendar before saving. |
| Subscribed calendar feed | The subscriber receives publisher updates after refresh. | Change the source and allow for the subscriber’s refresh schedule. |
| Imported ICS or CSV file | Events are copied at import time. | Treat later source changes as a separate migration or update task. |
Google explicitly notes that imported events do not stay synchronized between accounts, and that guest and conference information has import limits. A migration should therefore test representative events before importing a whole history.
Use the publisher’s sharing or subscription instructions when ongoing updates are wanted. Google documents calendar subscription and URL options. A private feed URL can function as an access secret; keep it out of public notes and screenshots.
Run a small two-device test
- Open the calendar service in a browser and identify the calendar that should own the event.
- Create an innocuous event named “Sync test” for a convenient future time, with no guests or sensitive details.
- Wait for normal synchronization and find it on the phone. Confirm the account, date, time, and calendar color/name.
- Change the title or time on the phone. Confirm that the browser copy changes.
- Add a second test event from the phone, explicitly choosing the same calendar. Confirm it appears in the browser.
- Test a recurring series in a temporary calendar, including one changed occurrence. Confirm the series and exception on both devices.
Record the observed delay instead of expecting an exact universal refresh interval. If the browser is correct and one device differs, investigate that device’s account selection, connectivity, calendar visibility, and background-sync settings. If the browser itself is wrong, investigate where the event was created or edited.
The calendar test log provides fields for the source calendar, device, event, and result. Clean up only the test events you deliberately created, after confirming their identity.
Distinguish a fixed instant from a local appointment
A timed meeting can represent one instant viewed in different local zones. A weekly local appointment can instead follow the wall clock in its specified region through daylight-saving changes. Choose the event’s intended zone and inspect future occurrences around a clock change. Google’s time-zone guidance explains its event and display settings.
Check all-day events separately. A birthday or conference day has a different meaning from a meeting fixed at midnight UTC. Preserve the intended date-only behavior during imports and migrations.
Resolve duplicates and missing events at their source
For duplicates, hide calendars one at a time. If the second copy disappears when an imported calendar is hidden, you have found a second source. Record both event locations before removing anything. A shared calendar, subscription, and repeated import can all produce visually similar copies.
For missing events, search the service’s browser view and inspect the event’s calendar field. Check whether a newly added calendar is enabled for display on the phone. For a one-way feed, verify the publisher’s current event and the subscriber’s refresh behavior before importing another copy.
Before replacing an account connection or bulk-cleaning a calendar, preserve unique local items and a supported export where available. Reconnecting an app should follow a diagnosis, because it can discard unsynchronized changes. Outlook users can continue with account and folder-level sync troubleshooting.
Continue exploring
- Outlook Sync: Mail, Calendars, Contacts, and Local Files
- Recall Email: Undo Send, Outlook Recall, and What to Do Next
- All software guides and earlier coverage
Product documentation checked September 7, 2026. Recheck your installed version, account plan, and organization’s settings when following product-specific steps.