Moving a store: what transfers and what must be ready first
A store move is several separate jobs, and only one of them travels in a product file. WooCommerce can export and import products as CSV, but its published schema covers product fields, not payment credentials or WordPress users, and nothing in it establishes that orders, email settings, or fulfillment connections move with it. Each of those needs its own owner and its own check. If the provider is Stripe, card data is transferred only to another PCI DSS Level 1 processor through Stripe's process, Link credentials are excluded, and that export does not include payment history. Provider approval does not move with the site: Stripe says a new account does not inherit a special status, and whether the existing account may serve the new domain is the provider's decision. Confirm every required item before customers are sent to the new store. Prism plans and carries out store moves under a written scope. Nothing here promises uninterrupted checkout.
For: An owner of a research-only peptide business preparing to move a store to another site or platform and then take orders there.
WooCommerce's built-in CSV tool exports and imports product fields such as name, price, stock, categories, and images. An image is imported from a directly accessible URL or from a file already in the media library. A redirected cloud-storage link is not supported. You cannot assign a specific post ID to a new product. Unrecognized columns are not imported. The published schema does not include a carrier account, a payment credential, or a WordPress user. A completed import means the importer finished that file. It does not mean every row was accepted, and it does not mean the store can take payment.
This page does not establish that WordPress users, order history, or email settings travel inside that CSV. Ask the implementer whether those items are in the migration scope, and leave them blank until the answer is specific. Do not fill the gap by assuming they copy.
Stored card data has its own rule, and only for the provider you asked
Stripe's payment-data export page says Stripe will transfer card data to another payment processor only when that processor is PCI DSS Level 1, with the attestation or registry listing and the encryption key Stripe requires. Credentials saved with Link are excluded. Stripe does not include payment history, subscriptions, or other objects in that file. Stripe also says never to send card details by ordinary message; the transfer is arranged with the receiving processor. You do not receive a spreadsheet of card numbers to import yourself.
Those limits are Stripe's. If the current provider is not Stripe, this page does not say whether any stored credential can move. Ask that provider in writing and leave the row unknown until it answers. Do not plan the release on the hope that saved cards, wallet credentials, or tokens appear on the new store.
The destination checkout and the payment account are separate gates
Before orders are sent to the new site, name its checkout type and payment extension. On WooCommerce, stores started after version 8.3 use the Checkout block by default, an incompatible gateway can leave no payment method, and compatibility is marked on the extension's WooCommerce.com product page. The system status report shows the site address, the checkout page, the active plugins, and the currency field. The currency field is the store's configured currency, not a provider's settlement currency.
Stripe says websites or businesses that operate independently need separate Stripe accounts, a new account does not inherit a special status, and each account is tied to one legal entity. After a live Stripe service is activated, the business origin country cannot be changed. Public business information, including the website URL and statement descriptor, is what the customer sees. Whether the existing account may be used for the destination domain is a question for the provider. Do not assume the old account's status covers the new site. Another provider's rule may differ. Ask that provider rather than applying Stripe's rule to it.
What makes a move bigger or smaller
Each item below is a separate responsibility, not part of a fixed bundle. Ask any proposer, including Prism, which of them the quote covers and who owns the ones it does not.
Catalog and images: how many products move, whether the images are reachable from a direct URL or the media library, and who checks the import against the schema.
Customers and order history: whether real customer accounts and past orders must move at all, and how they will be checked.
Stored payment credentials: whether the current provider will transfer any through its own process. That is arranged between processors, not handled as a file.
Destination checkout and gateway: which checkout type and payment extension the new store will run, and whether the provider permits the new domain.
Order emails: who rebuilds and reviews the destination's order-status emails.
Fulfillment: who reconnects the carrier, label, tracking, or warehouse account the destination will use.
Readiness: which release check the quote includes before customers are sent to the new store, such as a test order through the approved payment setup.
Each dependency needs an owner and a stop
WooCommerce documents a test order as a way to test a checkout. A release check is a test order on the destination, plus the open rows on this list, before customers are sent there. WooCommerce also sends particular emails when order statuses change, so the destination's email settings are their own item. None of this promises that the old checkout will keep working during the move.
You can decide that a row is confirmed, open, or out of scope. The implementer confirms the technical items it controls. The provider decides whether the destination arrangement can process.
In a Prism migration, this list is the release checklist: the catalog, domain, checkout, order emails, and payment arrangement each get an owner, and Prism carries out the parts in the agreed scope. The provider still decides account approval, and Prism confirms scope, responsibilities, fees, and terms before work begins.
In the consultation request, include the current and destination platforms, the approximate number of products, whether real customers or order history must move, your payment provider, and the date you intend to switch. Leave out card data, tokens, API keys, and customer lists.
Release dependency list
Mark each row confirmed, open, or out of scope in the last column, and name the person who can close it. Do not paste card numbers, tokens, or API keys.
Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.
Release dependency list. The last column is for temporary notes.
Dependency
What ready means
What not to assume
Owner and status
Public site address
What ready meansThe destination address is the one recorded on the new site, not a remembered address from the old status report.
What not to assumeChanging a product file does not change the domain. This page does not provide DNS steps.
Catalog
What ready meansA reviewed product CSV imported on the destination, checked against the schema, including images you confirmed are reachable.
What not to assumeImported products keep their old post IDs, or unrecognized supplier columns arrive by themselves.
Users and order history
What ready meansThe implementer has said, in writing, whether WordPress users and orders are in scope and how they will be checked.
What not to assumeA product CSV includes users, orders, or email settings. It does not.
Stored payment credentials
What ready meansThe current provider has said in writing whether any credential can move, and any Stripe transfer is Stripe's PCI-restricted process rather than a file you handle.
What not to assumeSaved cards, Link credentials, tokens, or payment history appear on the new store because the catalog moved.
Destination checkout
What ready meansThe checkout type and the named payment extension are installed, and any block-compatibility warning has been read.
What not to assumeA WooCommerce checkout claim means a payment method will be visible, or that a provider has approved it.
Provider permission for the destination
What ready meansThe provider has said in writing whether this domain and catalog may use the named account.
What not to assumeThe old account's status, or a new Stripe account, automatically covers the destination. Stripe says a new account does not inherit special status.
Order email on the destination
What ready meansThe destination's order-status emails have been reviewed. WooCommerce sends particular emails when statuses change.
What not to assumeEmail from the old site keeps sending for orders placed on the new site.
Fulfillment connection
What ready meansThe carrier or warehouse account used by the destination is confirmed with that vendor. Product shipping classes in a CSV are not that account.
What not to assumeA product import reconnects labels, tracking, or a third-party warehouse.
Release acceptance
What ready meansA test order on the destination succeeds through the approved payment setup, and every required row above is confirmed.
What not to assumeThe old store's last successful order, or the implementer's statement that the move is done, accepts the new checkout.
These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.
Limits
Nothing on this page promises uninterrupted checkout, or that an approval, a saved token, or card data will transfer.
Stripe's export limits apply to Stripe. They are not a rule for a provider this page has not read.
Confirm migration responsibilities separately; processing approval remains the provider’s decision. Confirm the fees and timeline for any agreed work. Do not send card data through the public form.
WooCommerce product CSV — checked 2026-09-21. The built-in CSV tool moves product data between stores. A new product cannot be given a specific post ID. Images come from a directly accessible URL or the media library, not from a redirected cloud link. Unrecognized columns are not imported. The schema covers product fields, not payment credentials or user accounts.
Stripe payment data export — checked 2026-09-21. Stripe transfers card data only to another PCI DSS Level 1 processor through its process. Link credentials are excluded. The export does not include payment history or other objects.
WooCommerce system status report — checked 2026-09-21. The report records the site address, checkout page, active plugins, and a currency field for displayed prices and payments processed in the store.
WooCommerce cart and checkout blocks — checked 2026-09-21. Stores started after WooCommerce 8.3 use the blocks by default. Incompatible gateways can leave no payment method. Compatibility is marked on the extension product page.
WooCommerce order statuses — checked 2026-09-21. WooCommerce sends particular emails when order statuses change, and those emails are configured in the email settings.
WooCommerce managing orders — checked 2026-09-21. WooCommerce documents test orders as a way to test a checkout flow or integration.
Stripe multiple accounts — checked 2026-09-21. Independent websites or businesses need separate Stripe accounts. A new account does not inherit a special status. Each account is associated with one legal entity.
Stripe account setup — checked 2026-09-21. After a live Stripe service is activated, the business origin country cannot be changed. Public business information includes the website URL and statement descriptor.
Prism solutions — checked 2026-09-21. The provider decides eligibility and account terms. Prism discusses scope, fees, and terms before a storefront or processing consultation.
Prism features — checked 2026-09-21. A website review does not guarantee approval or continued processing and is not a compliance certification.