TL;DR
Shopify Scripts hard-sunsets on June 30, 2026 — after that date, any merchant still on Scripts loses their custom checkout logic and Functions takes over entirely. Before you flip the switch, you want a frozen record of what your Scripts actually did (the code, the logic, the discounts they applied) and what your store's numbers looked like under them. Convert: Anything to PDF turns your exported script code (as text or Markdown), your config notes, and your store-report CSVs into clean PDFs — locally, no upload, no watermark, no account. It's the cheapest insurance policy for a migration that's easy to get wrong.
The short answer: snapshot before you migrate
Migrations are where logic quietly disappears. When you move from Shopify Scripts to Shopify Functions, you're rewriting checkout behavior in a new system — and if the new version behaves differently, you'll want to compare it against exactly what the old version did. The problem is that once Scripts is gone on June 30, 2026, you can't go back and read the old code or see the old behavior. So before you migrate: export your script source, write down the rules each script enforced, and pull the store reports that show how those scripts performed. Save all of it as PDFs you control. Ten minutes now saves a forensic nightmare later.
What's actually changing
Shopify Scripts (the Ruby-based checkout customization system that powered line-item, shipping, and payment discounts for Plus merchants) is being fully replaced by Shopify Functions. Shopify has set a hard sunset of June 30, 2026 — not a "deprecated but still runs" state, but an actual cutoff. If you haven't migrated by then, your Scripts stop executing. This lands in the same window as the broader Summer 2026 Editions push (Checkout Blocks, AI merchandising, Storefront API improvements), so a lot of Plus merchants are touching checkout config at once.
The migration itself is Shopify's domain and they've documented it. This post is about the part nobody documents: keeping a record of the old world so you can verify the new one.
What to archive before June 30
| Artifact | Format you have it in | Why archive it |
|---|---|---|
| Script source code | Ruby (text) | The exact logic, so you can confirm Functions reproduces it |
| Discount/rule documentation | Markdown or text notes | Plain-English record of what each script was supposed to do |
| Checkout config screenshots | PNG/JPG | Visual proof of the old setup |
| Sales/discount reports | CSV export | Baseline numbers to compare post-migration performance |
| AOV and conversion reports | CSV export | Detect if the migration changed checkout behavior |
Convert: Anything to PDF handles every one of those source formats — text, Markdown, images, and CSV — and can merge them into a single per-migration archive.
How to turn your exports into PDFs
- Install Convert: Anything to PDF — free, no account.
- For script code: paste it into a
.txtor.mdfile, then drop the file into the extension. Markdown gets typeset cleanly; plain text is preserved as-is. - For store reports: export the report from Shopify admin as CSV, then drop the CSV in. The extension auto-formats it into a readable table — and if it has 6+ columns (most sales reports do), it automatically switches to landscape so nothing gets clipped.
- For screenshots: drop your PNG/JPG checkout-config captures in.
- Merge them: drag all of them in together — code, notes, CSV, screenshots — and combine into one PDF in the order you want. There's no merge limit.
- Click Convert. The PDF downloads instantly. No watermark, no size cap.
Everything runs on your device using a bundled PDF library — your store data and customer numbers never touch a server. That's a real consideration: a sales-report CSV often contains revenue, discount codes, and customer-adjacent data you don't want to paste into a random online converter.
A realistic pre-migration packet
A clean structure a Plus merchant or their agency can hand off:
scripts-migration-2026/01-script-source.pdf— every Ruby script, typeset and readablescripts-migration-2026/02-rule-documentation.pdf— Markdown notes on what each didscripts-migration-2026/03-checkout-config.pdf— screenshots of the old setupscripts-migration-2026/04-baseline-reports.pdf— sales, AOV, and discount CSVs as tables
After you've migrated to Functions, you re-run the same reports and compare. If conversion dipped or a discount stopped applying, you have the exact before-state to diagnose against — instead of trying to remember how it used to work.
Why CSV → PDF beats "just keep the spreadsheet"
You'll keep the CSVs too, of course. But a CSV is a working file — it gets edited, re-sorted, overwritten, lost in a Downloads folder. A PDF is a frozen snapshot: this is what the numbers were on this date, formatted to read, impossible to accidentally change. For a migration baseline you want both: the CSV to analyze, the PDF as the immutable record. The auto-landscape handling for wide reports means the PDF is actually legible instead of a column-clipped mess — a small thing that matters when you're comparing two reports side by side months apart.
Note one thing the extension doesn't do: Excel (.xlsx) files aren't read directly. If your reports are in Excel, do File → Save As → CSV first (or in Google Sheets, File → Download → Comma-separated values), then drop the CSV in.
Beyond the migration
This same workflow — code/notes/CSV/images → one merged PDF — is useful well past June 30. App migrations, theme changes, payment-provider switches, and seasonal promo wind-downs all benefit from a frozen before-state. We built Convert: Anything to PDF to be the boring, reliable, free utility that's always there for this. It's part of a small catalogue of single-purpose tools — our manifesto explains why we keep them small, free, and local rather than bundling them into a bloated suite. If you also archive live store pages (a published policy page, a paywalled supplier portal), Convert: Web to PDF handles those.
Frequently asked questions
When exactly do Shopify Scripts stop working?
June 30, 2026 is the hard sunset. After that date Scripts no longer execute; Shopify Functions is the only supported checkout-customization system. Migrate before then or lose your custom logic.
Can I convert my Ruby script code to PDF?
Yes. Save the code into a .txt or .md file and drop it into Convert: Anything to PDF. Markdown is typeset; plain text is preserved. This gives you a frozen, readable record of the exact logic before it's gone.
Can it convert my Shopify CSV reports?
Yes. Export the report as CSV from Shopify admin and drop it in — it auto-formats into a table, and wide reports (6+ columns) auto-switch to landscape so nothing is clipped.
Can I convert Excel report files directly?
Not directly. Export to CSV first (Excel: File → Save As → CSV; Google Sheets: File → Download → CSV), then convert. The CSV path gives you the auto-formatted table.
Can I merge code, notes, screenshots, and reports into one PDF?
Yes. Drag in mixed formats — Ruby/text, Markdown, PNG/JPG, CSV — and combine them into a single PDF in any order. No merge limit, no file-size limit.
Will my store data be uploaded anywhere?
No. Conversion runs entirely on your device using a bundled PDF library. Revenue numbers, discount codes, and customer-adjacent data in your reports never leave your browser.
Are there watermarks or limits?
No watermarks, no file-size limits, no conversion caps, no account. It's free, funded by us rather than by ads or your data.
Bottom line
The June 30, 2026 Scripts sunset is a one-way door. Before you walk through it, freeze the old world: your script code, your rule documentation, and your baseline store reports, all as PDFs you own. Convert: Anything to PDF turns code, notes, screenshots, and CSVs into one clean merged archive — locally, free, no watermark. When the new Functions setup behaves oddly, you'll be glad you can see exactly how the old one worked.