The short answer
Storeshift accesses public storefront URLs and public listing pages, the same pages a shopper can open in a browser. It does not use your eBay credentials, seller dashboard, order history, buyer messages, private analytics, or authenticated eBay endpoints.
In hiQ Labs v. LinkedIn, the Ninth Circuit's 2022 decision said that accessing publicly available web pages likely does not violate the Computer Fraud and Abuse Act's ban on access without authorization. That is not a universal permission slip for every scraping project, but it is the key public-data rule buyers usually mean when they ask about legal to scrape eBay listings.
The other half of the answer is operational. Storeshift is intentionally narrow: product catalog conversion from public pages. It is not account automation, buyer-data export, order-history copying, or a way around eBay seller controls.
What Storeshift actually does
Storeshift turns your public storefront into a Shopify-ready catalog. The pipeline starts from the eBay store URL you provide, follows public listing pages, captures product facts, downloads public listing images, cleans the useful images, and writes a Shopify import CSV for your own store.
The run starts with a visible eBay store URL such as /str/yourstore.
Storeshift reads listing detail pages that can be viewed without logging in.
Product images are fetched from eBay's public image delivery system and re-hosted for Shopify import.
The final file is yours to inspect before importing into Shopify Admin.
What Storeshift doesn't do
Storeshift does not ask for your eBay password. It does not pull customer records, buyer addresses, order history, returns, messages, saved payment data, private traffic data, or anything else behind your seller login.
Storeshift also does not access eBay's internal APIs or authenticated seller endpoints. The first conversion flow is deliberately public-data only because that is enough to build the Shopify product catalog and it avoids credential risk for the seller.
How Storeshift keeps the boundary clean
The clean boundary is simple: public product pages in, Shopify CSV out. The worker resolves the storefront, collects listing URLs, reads visible product facts, downloads visible product images, and stops there. If a fact is not available on the public listing page, Storeshift does not pretend it saw it behind the seller dashboard.
That boundary also protects the customer. Since Storeshift does not receive eBay credentials, there is no password to store, rotate, or leak. Since it does not pull buyer data, the migration avoids the extra privacy risk that comes with names, addresses, order history, and private messages.
Public storefront conversion does not require eBay account access.
The product catalog is separate from customer data and order history.
The first-run pipeline does not call authenticated seller endpoints.
You inspect the preview and final CSV before products enter Shopify.
Your responsibility as the seller
Storeshift moves your product information into a Shopify import shape. The products are still your products, and the claims are still your responsibility. You need the right to sell the items, the right to use the photos, and accurate facts about condition, model, compatibility, price, brand, and quantity.
That responsibility matters when you syndicate from Shopify into other channels. If you plan to use TikTok Shop, Google Shopping, or another marketplace, review destination policies before pushing the imported catalog live.
If a listing already has a problem on eBay, migrating it to Shopify does not fix the underlying problem. A counterfeit item, unsupported compatibility claim, borrowed image, or inaccurate condition note needs seller review no matter which storefront hosts the product page.
What's legally settled and what isn't
The strongest settled point is narrow: accessing public web pages is treated differently from bypassing a login or technical gate. The hiQ decision is often cited for that point under the CFAA. It does not erase contract claims, platform terms, copyright questions, state law claims, or seller obligations.
Facts in a listing, such as price, brand, model, condition, size, and material, are generally not copyrightable by themselves. Photos are more sensitive. If you took the photos, they are yours to clean and reuse. If you used manufacturer images or another seller borrowed image, you are responsible for having the rights to use them in your Shopify store.
This guide is informational, not legal advice. If you have a specific dispute, a cease-and-desist letter, a restricted category, or a copyright concern, talk to a lawyer before migrating the catalog.
Why the free preview helps
The free preview lets you see exactly what Storeshift reads and writes before you pay. You can inspect the source products, the rewritten copy, the cleaned image set, and the Shopify CSV shape. If anything looks legally or commercially risky, you can stop before a full catalog conversion.
Related reading
Sources
FAQ
Do you need my eBay password?
No. Storeshift does not need your eBay password for the conversion run and does not access anything behind your eBay login.
What about the photos, do I own them?
If you took the photos, you generally control those photos. If they are manufacturer photos or images copied from another source, you are responsible for having the rights to use them in Shopify, the same as on your current eBay listings.
Is this how LitExtension and Cart2Cart work?
For product data gathered from public listing pages, the legal posture is similar. Broader migration services may request platform credentials or API access for customers, orders, and private store data, which is a different workflow.