Time Matters EWS Replacement Options, Ranked
If your firm runs Time Matters on a version before 2026 and syncs with Microsoft 365, your Exchange Synchronization depends on Exchange Web Services — the API Microsoft begins disabling October 1, 2026. There are exactly three ways to keep sync alive. Here's how they rank for a firm that wasn't planning an upgrade.
One Deadline, Three Doors
The facts, per Microsoft's EWS retirement FAQ: Microsoft begins disabling Exchange Web Services tenant by tenant on October 1, 2026, and shuts it down completely on April 1, 2027. Time Matters Exchange Synchronization on versions before Time Matters 2026 talks to Exchange Online over EWS — so when EWS goes, calendar, contact, and task sync with Outlook goes with it. Silently.
The vendor has a real answer: Time Matters 2026, released May 2026, moved Exchange Synchronization to the Microsoft Graph API with modern authentication, per the official release notes. The question is what it costs you to get there — and what your alternatives are if that path doesn't fit.
Every option below keeps your sync working. They differ in what they demand from you. We've ranked them by total cost, effort, and deadline risk for a firm on a pre-2026 version that wasn't already planning an upgrade. If your firm is current on AMP and due for an upgrade anyway, read Option 2 first — your ranking is different.
Option 1 — Bridge The Sync You Already Have
Exchange Sync Bridge sits between Time Matters and Microsoft 365. Time Matters keeps sending the same Exchange Sync (EWS) requests it sends today; the bridge translates them to Microsoft Graph — the API Microsoft is keeping. Nothing else changes: no Time Matters upgrade, no AMP renewal, no retraining, no data migration.
- Cost: $40 per sync-enabled user per month, no setup fees, no minimum term.
- Effort: Hosted setup typically takes minutes, plus a one-time Microsoft 365 admin consent.
- Risk: Low. Your current, known-good Time Matters version stays exactly as it is. Your data passes through and is never stored, and sign-in runs through Microsoft — we never see a user password (details here).
- Deadline fit: Works before, during, and after both EWS deadlines. No allowlist needed.
The honest caveat: not every application uses Exchange Sync identically, so we confirm fit before you pay anything — send us your Time Matters version and what you synchronize, and we'll tell you plainly whether the bridge covers it (how compatibility review works).
Option 2 — Upgrade To Time Matters 2026 (Requires Active AMP)
The vendor's fix is genuine and, for some firms, the right one: Time Matters 2026 syncs with Microsoft 365 over Microsoft Graph. If your firm is current on AMP, was planning the upgrade anyway, and has a consultant lined up, this path makes sense — confirm the specifics for your environment with your consultant or the vendor, in writing, before October 1.
For everyone else, the catches are real:
- The gate: upgrades require an active AMP membership. If AMP lapsed, the vendor path starts with reinstating it.
- The project: an upgrade is a project — scheduling, testing, data conversion, staff adjustment — normally spread over months. Running it under deadline pressure, in the same quarter every other affected firm is trying to book the same consultants, is its own risk.
- The price: you're paying for an upgrade you didn't plan, to fix a problem Microsoft created, on Microsoft's timeline.
If you're on Time Matters 2026 already, none of this applies to you — you're covered.
Option 3 — Microsoft's Allowlist (Buys You Until April 1, 2027)
Microsoft lets tenant administrators explicitly re-enable EWS (EWSEnabled) and allowlist specific applications by AppID, which extends EWS access past October 1, 2026 — we walked through the configuration in our post on extending the deadline.
- Cost: Free, beyond admin time.
- Effort: An Exchange Online admin task, plus the work of inventorying every EWS-dependent application so nothing is left off the allowlist.
- Risk: It feels like a fix, and it isn't. On April 1, 2027, the allowlist stops mattering — EWS is gone for everyone, with no exceptions. It ranks last not because it's bad, but because it's a delay, and delays are only useful if you use them to decide between Options 1 and 2.
Used deliberately — "we'll allowlist now and migrate calmly in Q1" — it's a perfectly good tactic. Used as the strategy, it's how firms end up in a worse panic six months later.
Which Door Is Yours?
Current on AMP and planning to upgrade anyway? Take the vendor path and schedule it now. Need time to decide? Flip the allowlist and use the months it buys. Staying on your current version — by choice or by budget? Bridge it and be done this week.
Not sure which option fits your firm?
Tell us your Time Matters version and what you sync today. We'll tell you plainly where you stand — including when the honest answer is "take the vendor path."
Find Out If You're Impacted
Exchange Sync Bridge