Your Exchange integration stops working on 1 October.

Software vendors with an Exchange or Microsoft 365 integration: scheduling and booking tools, CRMs, room booking, email signature managers, ticketing, archiving, anything that uses the EWS Managed API, ews-javascript-api, or raw EWS SOAP calls. Also internal teams with EWS scripts and services. If you're not sure whether you use EWS, that's what the assessment is for.

Within three business days of access to your integration code or documentation, you get:

• Every EWS operation your product uses, mapped to its Microsoft Graph equivalent or flagged where none exists.
• The gaps that need a decision: archive mailboxes, folder-associated items, some delegate and impersonation scenarios, Exchange management operations.
• Authentication changes: from EWS basic or OAuth patterns to Graph application or delegated permissions, with the admin-consent implications for your customers.
• Notification changes: EWS streaming and push subscriptions to Graph change notifications, with the differences in behavior.
• Throttling and pagination differences that affect your sync logic.
• A staged migration plan with a regression test list and a rollback path.
• A fixed price for Step 2.

The assessment is useful even if you migrate internally. If you proceed to Step 2, the $500 is credited.

Payment, calendar, and accounting integrations are what I do: OAuth lifecycle, idempotent sync, and state reconciliation across third-party APIs. Read the ClearWIP write-up for the depth of work: How I engineered ClearWIP. Every customer you serve hits the same October deadline, so the migration has to be right the first time.