Prepare a scoped store-data handoff so the incoming operations team receives the records and definitions it needs without unnecessary customer information or payment secrets. Product exports, reports and a complete recoverable backup serve different purposes.
IN THIS ARTICLE
01 Agree the handoff requirements
List the required datasets, date range, format and intended recipient. Common needs include products, open orders, stock, refunds and operational settings. Identify the authoritative system for each dataset when accounting, fulfilment or inventory also exists outside WooCommerce.
02 Choose supported export methods
- Use the built-in product CSV exporter for supported catalogue data.
- Use the relevant WooCommerce report export, approved order-export tool or authorised API integration for the required operational records.
- Check extension-specific export documentation for subscriptions, bookings or other custom records.
- Create a separate complete backup if recovery or ownership transfer also requires it.
- Verify the export counts, columns, currency, timezone and identifiers against the source.
- Transfer the files privately and confirm receipt by the approved recipient.
Does a product CSV contain the store's order history?
No. It is a catalogue export, not a complete business archive. Likewise, an analytics report may aggregate or transform data and is not necessarily a lossless order migration file. Match the export method to the operational question the recipient needs to answer.
Should I send the whole database?
Only when the recipient is authorised to receive that scope and a full database is actually required. It can contain personal data, credential material and unrelated application settings. A targeted export is often more appropriate for an operations report or limited transition.
03 Document the meaning of the data
Explain order statuses, custom fields, displayed order numbers versus internal IDs, tax treatment and the cutover time. Include open exceptions such as pending refunds or unfulfilled backorders. Do not silently omit difficult records that the incoming team will later need to reconcile.
04 Complete the transition
Confirm the recipient can use the export and compare a small sample with the live store. Agree retention and deletion for temporary copies. Transfer ongoing access through named accounts and separate API credentials, then revoke outgoing access after the handoff is verified. Preserve an approved handoff record without embedding secrets or unnecessary customer details.