301 redirects

When you move a store to Shopify, the URLs of your products and collections usually change. A product that lived at /old-catalog/blue-widget.html on the old platform becomes /products/blue-widget on Shopify. Without a redirect, every old link, bookmark, and search-engine result for that product lands on a 404.

Graftport can create those redirects for you. It looks at every product and collection it migrated, compares the old address to the new Shopify address, and creates a 301 redirect from old to new wherever they differ. If your source store is also on Shopify, any redirects you had set up there are carried over too.

When to run it

Generate redirects after a load finishes. The redirects are built from the live Shopify addresses of your products and collections, so the products need to be on Shopify first. If you load again later (for example after fixing a mapping), just generate redirects again. It only touches what changed, so running it more than once is safe.

How to start it

1. Open the migration and go to the Configuration tab.
2. Find the 301 redirects card and click Generate redirects.

The button is unavailable while a run or a purge is in progress, and while a Shopify shop domain and admin token have not been added yet. The reason is shown next to the button.

Watching progress

Once started, a progress banner appears at the top of the migration page and updates as redirects are pushed. It shows how many redirects were pushed out of the total, split into:

• Carryover — redirects brought over from a Shopify source store.
• Derived — redirects created from product and collection address changes.
• Failed — redirects Shopify rejected (rare; usually a path already in use).

When it finishes, the banner shows a short summary. A source check line may appear: it samples a few of the old addresses and reports how many were still live on the source store, which is a quick sanity check that the redirects point away from real pages.

Stopping it

Click Stop in the progress banner to cancel. Redirects already pushed stay in place; the rest are left untouched. You can generate redirects again at any time to finish the job.