antwork.fr/platform-migrations
Platform migration offer
I migrate Atlassian Connect apps to Forge and Shopify apps off script tags and non-expiring tokens, at a fixed price agreed before work starts. The dates below are set by the platforms; none can be pushed back by the app's publisher.
The deadlines
| Date | Platform | What changes |
|---|---|---|
| March 2026 | Atlassian | A Connect app can no longer ship Marketplace updates through its Connect descriptor; updates need a Forge manifest (Atlassian). |
| 1 Oct 2026 | Atlassian | A Connect app keeps 75% of its Marketplace revenue. A Forge app keeps 100% of its revenue up to $1M of lifetime Forge revenue per partner, then 83%, if it has no Connect modules, uses OAuth authentication and a Forge UI (UI Kit or Custom UI); revenue earned on Connect does not count (Atlassian). |
| 31 Jan 2027 | Atlassian | Connect end of support: critical security fixes only, capabilities removed on shorter notice, some apps may stop working without advance notice (Atlassian). |
| 1 Oct 2026 | Shopify | Script tags can no longer be created or updated, on every API version; existing ones keep running (Shopify). |
| 1 Jan 2027 | Shopify | Public apps must call the Admin API with expiring offline access tokens; non-expiring tokens get authentication errors (Shopify). |
| 1 Mar 2027 | Shopify | Shopify stops injecting script tags into storefronts. The replacement is an app embed block, which each merchant switches on in the theme editor, or a web pixel for analytics-only scripts (Shopify). |
Packages
Each package is a fixed price for one app, set in a written quote before any work starts. Prices are in euros, excluding VAT.
| Package | Platform | Scope | Price |
|---|---|---|---|
| Migration diagnostic | Atlassian | Read-only review of the Connect app: each module mapped to its Forge equivalent, data and auth changes, risks, and a fixed quote for the migration | 900 €, credited in full against the migration |
| Light migration | Atlassian | Forge manifest adopted and every module moved to a direct Forge equivalent, backend kept where it runs (Forge Remote). The migrated app has no Connect modules or scopes, uses OAuth authentication and a Forge UI: the three conditions for 0% revenue share under $1M | from 3,900 € |
| Standard migration | Atlassian | Modules with no direct equivalent rewritten, data moved to Forge storage or auth flow rebuilt. The migrated app meets the same three conditions | from 11,900 € |
| Token migration | Shopify | Expiring offline access tokens: token exchange for existing shops, refresh handling, storage | from 900 € |
| Script tag migration | Shopify | Each script tag replaced by an app embed block in a theme app extension, or by a web pixel for analytics-only scripts, plus the merchant activation notice | from 1,800 € |
| Both | Shopify | Token migration and script tag migration together | from 2,500 € |
For Shopify apps, the quote is free once I have read access to the code.
How a migration runs
You keep control of your code and your listing at every step: I deliver a pull request, you merge and publish.
- A short call.
- The services agreement signed, with a statement of work for the diagnostic (Atlassian) or for a free code review (Shopify); then read-only access to the repository.
- Diagnostic or code review: written scope, fixed price and delivery date.
- Migration statement of work signed, deposit invoiced.
- Work on a branch of your repository, against your development environment (a Forge development environment, or a Shopify development store), with tests for each change.
- Delivery as a pull request: test results, migration notes, rollback steps, and for Shopify the text and link that tell merchants to switch on the app embed.
- You review, merge and publish under your own partner account; I stay available during the release.
- Any reproducible defect in the delivered scope reported within 30 days of acceptance is fixed at no cost.
What you get, what I need
| You get | I need from you | Stays with you |
|---|---|---|
| The migrated code in a pull request on your repository | Read access, then write access to one branch | Merging, deploying and publishing |
| Test results and a written list of what changed | A development environment and test accounts | Your Marketplace or App Store listing and partner account |
| Rollback steps | Answers on product decisions the migration raises | Pricing, support and communication with your customers |
| For Shopify, the merchant notice to switch on the app embed | Ongoing maintenance, unless quoted separately |
Confidentiality, tools and warranty
- Confidentiality. The agreement covers your code, credentials and business information, for five years after the work ends. Access is limited to what the work needs, and you revoke it once the last statement of work ends; your code is never reused for another client.
- Personal data. I work on development environments with test data and do not need your customers' production data. If a migration requires it, we sign a data processing agreement first, and that data is never processed with AI tools.
- How I work. I no longer write code by hand: I frame the work, split it into deliverable steps and drive the production with Claude Code (Anthropic). Every change is reviewed by a separate agent on a fresh context before each pull request, sensitive paths such as tokens and auth get a dedicated security review, and I decide what ships. With model training turned off in my account, Anthropic states that it keeps session data for 30 days and does not use it to train models, except content flagged for a safety review (Anthropic). If your policy excludes AI coding tools, tell me before the quote.
- Warranty. Any reproducible defect in the delivered scope reported within 30 days of acceptance is fixed at no cost. Liability is capped at the price of the statement of work.
Who I am and how to start
Louis Rotellini, AI Product Engineer · Full-Stack · Next.js · TypeScript · Node.js, independent developer based in France (Louis Rotellini EI, SIREN 800 503 476). More at antwork.fr.
Products I publish under my trade name, Antwork:
- Antwork Field Editor: Quick Edit, Bulk Edit and admin columns for ACF and SCF fields, on WordPress.org.
- Glass Headers: modifies HTTP request and response headers, on the Chrome Web Store.
- Tracing Paper: overlays a design mockup on a web page to check it pixel by pixel, on the Chrome Web Store.
To start, reply with the app concerned and who can grant read access to its repository; the diagnostic or quote follows from there.
Sources
- Announcing Connect end of support: timeline and next steps, Atlassian
- Getting ready for Connect end of support, Atlassian
- Extended timelines for Marketplace revenue share changes, Atlassian
- Pricing, payment and billing, Atlassian
- Online store script tags deprecation, Shopify
- Expiring offline access tokens required for all public apps as of January 1, 2027, Shopify
- Data usage, Claude Code documentation
- Consumer Terms, Anthropic