Legacy-store migration sheet
Yenra | September 10, 2026
https://yenra.com/yahoo-merchant-solutions/

Keep this record private. Inventory current providers and account ownership before changing routing. Confirm supported exports with current documentation/support. Rehearse a representative import and checkout before scheduling a production move.

Store/service identifier and current plan:
Current provider, verified support route, account owner:
Dependency owner and export/configuration location for:
  Catalog, variants, images, stock:
  Open/historical orders, refunds, fulfilment:
  Domain registrar, nameservers, complete DNS records:
  Email provider, routes, sending settings:
  Payment provider, subscriptions, integrations:
  Templates, policies, content, old/new URL map:
Export timestamps and untouched-original storage:
Data minimization, access controls, retention responsibilities:
Sample import counts and semantic checks:
Variant IDs, parent relationships, options, stock, prices:
Checkout, totals, notification, fulfilment, refund tests:
Redirect and missing-page tests:
Known discrepancies and repairs:
Final data cutoff timestamp/timezone:
New orders/stock updates reconciliation owner:
Routing change owner and verification:
Recovery trigger, decision owner, reversal procedure:
Orders placed after cutover: recovery reconciliation procedure:
Agreed overlap/verification period before old-service closure:
Website, email, payment, staff-workflow sign-off:

Fictional count check: 120 parent products with 360 sellable variants need both counts AND every variant relationship verified. An equal parent-product count alone does not establish a complete import.
Current documentation entry: https://help.turbify.com/article/store-manager-index