Rewrite for Microsoft Graph, or keep your EWS code?
Microsoft's advice is to rewrite EWS code for Microsoft Graph. For an application with a handful of calls that is a reasonable job. For code that has grown over years it is a project with a fixed deadline: April 1, 2027. You can do it yourself, have us do it, or keep the code and swap one package.
| What matters | Rewrite it yourself | We rewrite it for you | Sunsetless EWS |
|---|---|---|---|
| What changes | Every EWS call and the code around it. Items, folders, IDs, paging, search and error handling all work differently in Graph. | The same calls, rewritten by us. Your team reviews the change. The new code is yours and depends on nothing from us. | One package reference and four configuration values. Namespace, types and methods stay the same, so your code compiles unchanged. |
| How you know it behaves the same | You write the comparison tests yourself, and you need to know what EWS returned in every case your application relies on. | We run your application’s calls through live EWS and through Graph and send you every difference we found. | 212 scenarios were run through live EWS and through the library and compared field by field. Every known difference is published. |
| After April 1, 2027 | Exchange Online no longer answers EWS, so there is nothing left to compare a rewrite against. | The same applies, so we compare your application with EWS while Exchange Online still answers it. | The comparisons were recorded while EWS was still running, and they are replayed as regression tests on every build. |
| Mailboxes on-premises and in the cloud | Two code paths to build and keep in step: Graph for Exchange Online, EWS for Exchange Server. | Two code paths, built by us, that your team keeps in step afterwards. | One code path. Calls for Exchange Online go to Graph, calls for on-premises Exchange stay on EWS. |
| When Microsoft Graph changes | Your team follows the changes and fixes what breaks. | Your team owns the code and follows the changes, as with any other Graph code. | We follow them for you. Every future version is included in the one-time price. |
| What Graph cannot do | You find the gaps one by one while rewriting. | The free check names the gaps before you pay anything. | The same gaps apply: public folders have no Graph API. They are listed before you buy, and the library answers them with a clear EWS error. |
| What it costs | Developer time, in proportion to the number of call paths, plus the comparison tests above. | From $1,000 for a few EWS operations, more for each further one. A fixed price after a free check, and no license. | From $899, paid once. No subscription, and every future version is included. Free to try with your code for 14 days, and a 14-day money-back guarantee after you buy. |
What we bring to a rewrite
To build Sunsetless EWS we worked out how each operation of the EWS Managed API maps to Microsoft Graph, and compared 212 scenarios with live EWS, field by field. We know where item IDs, extended properties, recurring meetings, paging, search filters and notifications behave differently, and which calls Graph cannot make at all.
A rewrite by us starts from that list. You get a fixed price after a free check, and the code is yours when we are done.
Who does the work

Jacek Marchewka
Founder of Sunsetless
I do, from the free check to the last review. I have written C# and .NET for a living since 2013.
I am a lead .NET developer on a UK payroll platform used by 250+ organizations, in the team that sets backend standards for 18 .NET product teams. Before that I worked on a shift management platform used by dozens of UK hospitals.
Moving EWS code to Graph is rarely only about the EWS calls. The change reaches the code that stores item IDs, the jobs that sync calendars, the retries and the tests around them, often in an application on .NET Framework that nobody has opened for years. That part needs someone who has kept large .NET systems running in production.
What about rewriting with an AI agent?
An agent drafts Graph code quickly, and it is a good way to start a rewrite. It cannot tell you what EWS returned for your folders, your recurrence patterns and the IDs in your database, and that is what the new code has to match.
Someone still has to compare the old behavior with the new one, path by path, and after April 1, 2027 the old behavior is gone. If you take that route, record your EWS responses while you still can.
When Sunsetless EWS fits
- Many EWS call paths: search filters, extended properties, sync, notifications, calendars.
- Hybrid setups, where EWS has to stay for the on-premises mailboxes.
- A product you ship to customers, whose tenants lose EWS at different times.
- Code that works and that nobody wants to reopen before the deadline.
When a rewrite by us fits
- You want no third-party library and no license in the application.
- Your team has no time for the rewrite before the deadline.
- You want the new code compared with live EWS while that is still possible.
When your own rewrite fits
- Your application makes a few simple calls, such as sending mail or reading one inbox.
- You are replacing or retiring the application anyway.
- It depends on public folders in Exchange Online. No library can route those to Graph.
You can still move to Graph later, one module at a time, while the rest keeps running on Sunsetless EWS.