SuiteScript 1.0 to 2.1 Migration: Sign-Ups Are Open
September 7, 2026 · 2 min read
Sign-ups for the SuiteScript 1.0 to 2.1 migration service are open: suiteresources.com/signup.
Before you click: this isn't first-come, first-charged. Submitting the form reserves your place — nothing goes on your card or is drawn via ACH. I'm onboarding in small batches and will email you a payment link once your spot opens up. Going slowly is the whole point, so it felt wrong to abandon that the moment sign-ups opened.
What Actually Happens
You give me four things: name, email, company, and — optionally — a sentence or two about your account. No twenty-field intake form.
You'll get a payment link and a choice: card or bank transfer. Everyone starts at Tier 1 regardless of where they think they'll land. If migrating your chosen scripts moves you to a higher tier, I'll let you know and send a payment link for the difference.
What You're Actually Buying
The full breakdown is on the migration page, but the short version:
- A catalog of your SuiteScript estate, scored for complexity against Oracle's own published matrix and for risk separately — not my arithmetic, so it survives scrutiny from someone senior.
- Conversions you can prove, with regression tests built from your original 1.0 source, not the 2.1 output. Tests written from the conversion just encode the mistake and pass.
- A real, deployable SuiteCloud project — delivered into a repository you nominate, or a zip if you'd rather not connect anything. The 1.0 originals stay alongside it, so a revert is a git operation, not an archaeology dig.
Pricing runs in five tiers by script count, starting at $2,000 for the first ten. You see the catalog, decide how far you actually need to go, and pay the difference to move up — nobody commits to a five-figure number before they've seen what's in the account.
Why Batches
Three hundred scripts done carefully takes longer than three hundred scripts done fast, and I'd rather be the one who does it carefully. An approval step only means something if the approver has time to actually read what they're approving. Opening this to everyone at once and rushing the queue would undo the entire reason to hire someone who's done this before instead of running a script unattended.