How OneNote Mobile Synced in Windows Mobile 6.5

This article provides an overview of how OneNote Mobile synchronized data on devices running the Windows Mobile 6.5 operating system. Before modern cloud-first architectures became the industry standard, Microsoft utilized local synchronization software, tethered connections, and dedicated desktop software integrations to keep mobile notes aligned with desktop notebooks.

The Synchronization Framework: ActiveSync and WMDC

In the Windows Mobile 6.5 era, OneNote Mobile did not natively sync directly to the cloud via services like OneDrive. Instead, it relied on physical or local wireless connections to a host PC using Microsoft ActiveSync (on Windows XP) or Windows Mobile Device Center (WMDC on Windows Vista and Windows 7).

Users connected their Windows Mobile 6.5 handheld device to a personal computer via a USB cable or a paired Bluetooth connection. Once connected, ActiveSync or WMDC recognized the device and initiated a partnership protocol configured to sync specific types of personal information, including contacts, calendar items, and OneNote data.

The Desktop Integration

For OneNote Mobile to sync, the host PC was required to have Microsoft Office OneNote installed (typically OneNote 2007 or OneNote 2010).

During the initial sync configuration:

  • Users selected "OneNote Mobile" within the sync options in ActiveSync or WMDC.
  • The desktop version of OneNote created a dedicated notebook or section specifically labeled "OneNote Mobile."
  • Only files placed in this designated mobile section were synchronized with the Windows Mobile 6.5 device, rather than the user's entire collection of desktop notebooks.

Data Transfer and Two-Way Synchronization

The synchronization process operated as a two-way exchange:

  1. Mobile to Desktop: Notes created on the Windows Mobile device—which supported plain text, simple lists, pictures taken with the device camera, and voice recordings—were transferred directly to the designated "OneNote Mobile" section on the PC upon connection.
  2. Desktop to Mobile: Pages created or edited inside the mobile section on the desktop client were pushed down to the mobile device.

Because the mobile hardware of the era had limited processing power and memory, rich desktop formatting (such as complex tables, extensive ink drawing, and embedded files) was either stripped down, converted to static images, or marked as read-only to ensure compatibility with the mobile application.