gSyncit is an Outlook add-in that copies calendar events, contacts, tasks, and notes between selected Outlook folders and supported cloud accounts. Each connection is a mapping: one Outlook collection is paired with one remote calendar, address book, task list, or note location. This differs from exporting a file once. gSyncit compares both sides again during later runs and applies the direction, filters, and conflict rules saved in that mapping.
Mappings define scope
A calendar mapping names the Outlook calendar, remote account, and remote calendar that belong together. Contacts, tasks, and notes use their own mappings. Authorizing a Google account does not make every Google collection synchronize automatically; the user still selects the specific remote list and Outlook folder.
This boundary is the first troubleshooting check. A valid account can coexist with a disabled mapping or a mapping aimed at the wrong calendar. If one data type stops while others continue, rebuilding that single mapping can be more direct than changing the shared account or reinstalling the whole add-in.
First-match risk
Before the first synchronization, the developer recommends backing up Outlook and checking both sides for duplicates. gSyncit tries to match existing records by fields such as title and date, task due date, or contact identity. Records that look different enough can remain unmatched and then appear twice after synchronization.
The duplicate-removal wizard can inspect Outlook folders, but cleanup after a broad first run is slower than preparing the source. An abbreviated contact name on one side and a full name on the other may represent one person to the user while remaining two records to matching logic. A small test mapping is safer than opening every folder at once.
Direction after reset
Each mapping has a primary source for its initial run or a mapping reset. The primary side supplies the preferred record when gSyncit establishes the relationship between existing items. After that stage, modification times help decide which change travels in which direction.
The choice becomes important when several computers synchronize Outlook through the same remote account. The recommended arrangement uses Outlook as primary on the main computer and the remote service as primary on the additional computers. Marking every local Outlook store as primary can make several machines push competing assumptions during a reset.
Shared calendar trap
gSyncit can connect several Google calendars to one Outlook calendar by assigning a unique Outlook category to each mapping. The category tells the add-in which remote calendar should receive each local event. An event without the expected category can travel to every mapping that points at the shared Outlook calendar and create copies across several remote calendars.
Separate Outlook calendars avoid that ambiguity and are the less error-prone arrangement recommended in the documentation. If one combined calendar is required, every mapping needs a distinct category and local events need the correct assignment before the sync. Category colors alone are not enough unless the mapping uses those categories as routing rules.
Notes become documents
Outlook notes can map to a Google Drive folder, where gSyncit treats them as plain text documents. This keeps the words available outside Outlook, but Outlook-specific formatting and behavior do not become a full cloud note application. Editing the remote text changes the content that returns during the next eligible sync.
Filters can limit synchronization by keyword or Outlook category, and one-way settings can stop changes from returning in the opposite direction. These controls belong to each mapping. A contact filter does not silently govern the calendar, and changing one mapping cannot repair an unrelated task list that points to the wrong account.
