Stocky is shutting down on August 31, 2026 — rescue your data before it's gone

bubobo — Mon, 15 Jun 2026 13:41:49 +0000

If you run a Shopify store and use Stocky for purchase orders and inventory, mark the date: Shopify is shutting Stocky down on August 31, 2026. It was already removed from the App Store in February 2026, and some features (min/max forecasting, transfers) were cut back in 2025.

Here's the part that catches people out: your Stocky data does not move to Shopify automatically. Your purchase orders, stocktakes and inventory reports won't be there after the shutdown unless you export them yourself first. And there's a nastier gap — Stocky can't export your suppliers at all, and there's no location-level inventory export. Your supplier names, lead times and per-product costs effectively only live inside your purchase orders.

What to do before the deadline

Export what you can from Stocky now. Use Stocky's built-in reports to export purchase orders and stocktakes as CSV. Don't leave it to the last week.
Rebuild what Stocky won't export. Your suppliers and costs are buried in those PO exports. You can reconstruct them by hand in a spreadsheet… or use a tool.
Pick a replacement (Shopify's native POs, or a third-party inventory app) and import your rescued data.

For step 2, I built a free tool: Reordo. Drop in your exported Stocky CSVs and it rebuilds a clean supplier list and a supplier × product × cost catalog you can import anywhere, plus a backup of your POs and total inventory value. It runs 100% in your browser — nothing is uploaded (handy when you're dealing with cost data). Disclosure: I made it.

Whatever replacement you choose, the important thing is to get your data out before August 31. After that, it's gone.

Microsoft is retiring EWS in 2026 — how to find every EWS call in your codebase

bubobo — Mon, 15 Jun 2026 13:41:28 +0000

If your apps talk to Exchange Online over Exchange Web Services (EWS), the clock is ticking. Microsoft is retiring EWS for Exchange Online, with blocking starting October 2026. After that, EWS requests to Exchange Online stop working and you must use the Microsoft Graph API instead. (On-premises Exchange isn't affected the same way.)

The migration itself is well documented. The annoying part is the first step: figuring out where your code actually touches EWS — especially in older or large codebases spread across .NET, Java, Python and PowerShell.

Here's a practical checklist of what to look for, and what each maps to in Microsoft Graph.

What EWS usage looks like

Connection & auth

Microsoft.Exchange.WebServices namespace, new ExchangeService(...), ExchangeVersion
AutodiscoverUrl(...) — Graph has no Autodiscover; use the fixed endpoint https://graph.microsoft.com/v1.0
WebCredentials / basic auth — replaced by OAuth2 via MSAL (delegated or app-only)
exchangelib (Python), New-WebServiceProxy (PowerShell), microsoft.exchange.webservices (Java)

Operations → Graph equivalents

EWS	Microsoft Graph
`FindItems` / `ItemView`	`GET /me/messages` (`$filter`, `$search`)
`EmailMessage` + `SendAndSaveCopy`	`POST /me/sendMail`
`FindFolders` / `WellKnownFolderName`	`GET /me/mailFolders`
`Appointment` / `CalendarFolder`	`/me/events`, `/me/calendar`
`GetUserAvailability`	`POST /me/calendar/getSchedule`
`ContactsFolder`	`/me/contacts`
`SyncFolderItems`	delta query `GET /me/mailFolders/{id}/messages/delta`
`StreamingSubscription` (pull/push)	Graph change notifications (`POST /subscriptions`) + webhook
EWS impersonation (`ImpersonatedUserId`)	app-only auth + target `/users/{id}`

A faster way to scan

Grepping by hand works, but it's easy to miss things. I built a small free tool for exactly this: EWScan. Drop in your project as a .zip (or individual files) and it lists every EWS reference — file, line, and the Microsoft Graph replacement for each — so you can scope the migration. It runs entirely in your browser; your source code is never uploaded. (Disclosure: I made it.)

Migration tips

Start with auth: set up MSAL + register an app in Entra ID, then port one read path (e.g. list messages) end-to-end before the rest.
Prefer application permissions + /users/{id} where you used impersonation.
Replace SyncFolderItems polling with delta queries, and EWS subscriptions with Graph change notifications.