Two fixed-price services, both off your own scan report
The scanner is free and MIT licensed, and it deliberately does not migrate anything. These are the two pieces of work that start where the report stops: drafting the change, and planning around the call sites Microsoft Graph does not replace.
Drafted Migration PR
$199 USDA drafted, human-reviewed migration pull request for up to 10 migratable EWS or QuickBooks call sites from your DeadlineScan report. Opened on your repo (or delivered as a patch file) within 72 hours. A draft for your review — it compiles, and your existing tests pass where tests exist.
What you get
- One pull request opened on your repository, or a patch file if you would rather not grant write access.
- Up to 10 call sites, chosen from the findings your report classifies as migratable.
- Every call site reviewed by a named human before delivery.
- Delivery within 72 hours of the report and repository access reaching us.
Scope cap
Ten call sites per pull request. Larger estates are quoted by email — send the report and we will scope it rather than split it into ten-packs.
Call sites the mapping table classifies as a gap — public folders, online archive, group mailboxes, mailbox import/export, and the dropped QuickBooks report — are not migratable and are not in this service. They are what the runbook below is for.
Reserve: Migration PRCheckout opens shortly — email to reserve a slot.
Parity-Gap Runbook
$149 USDA scoped, human-reviewed runbook for EWS call sites with no Microsoft Graph equivalent (public folders, archive access, Group mailboxes, import/export): the allow-list configuration that keeps them running until March 31, 2027, plus a concrete plan for the April 2027 shutdown. Tailored to your scan report; delivered within 72 hours.
What you get
- The
EwsAllowedAppIDsconfiguration for the applications your report shows are still calling EWS, written against your own findings rather than a generic checklist. - A per-gap plan for the April 2027 shutdown: what the content or operation moves to, and what has to be decided before the runway ends.
- Reviewed by a named human before delivery.
- Delivery within 72 hours of the report reaching us.
Scope cap
One report, one runbook. Multi-tenant estates and portfolios are quoted by email.
Reserve: Parity-Gap RunbookCheckout opens shortly — email to reserve a slot.
How it runs
- Run the free scanner and keep the JSON report:
deadlinescan scan ./my-repo --json report.json. Scanning is local; nothing is sent anywhere. - Email the report to hello@deadlinescan.com with which service you want. For a pull request, say which route you want: collaborator (write) access so the pull request can be opened on your repository — on a public repository a fork works instead — or a patch file, for which read access is enough.
- The 72-hour clock starts when the report and, for a pull request, the access or the code reach us.
The scanner never sends your code anywhere. The paid services are different by nature: they review what you choose to send. What we keep, and for how long.
If a delivery misses the 72-hour SLA, or the draft is unusable and one revision does not fix it, the payment is refunded in full. Refund terms.
Why a draft and not a migration
Both deliverables are drafts for your review, not a warranty that your integration is finished. A pull request that compiles and passes your existing tests is a starting point a reviewer can read in an afternoon; it is not a claim that every behaviour of the old call survived the move. Where the mapping table says a replacement differs — OData filter syntax against EWS restrictions, Graph's item schema against EWS extended properties, subscription lifecycle against EWS notifications — the difference is called out in the pull request rather than papered over.