A legacy Yahoo Merchant Solutions store is a collection of business dependencies: products, orders, page URLs, domains, email, payments, and custom behavior. Whether you are keeping it in service or moving it, first identify who controls each dependency and demonstrate that the records and customer tasks survive the proposed change.
Establish which service and account you have
Yahoo Merchant Solutions belongs to the history of Yahoo's small-business storefront services. In June 2022, Infinite announced its acquisition of the former Yahoo Small Business portfolio from Verizon. Infinite's small-business page identifies Turbify as its business providing domains, websites, hosting, and stores.
Use your current invoice, account dashboard, and verified support channel to establish the actual service, plan, account owner, and supported export tools. Historical package names and limits cannot determine your present entitlement. Record the store identifier and administrative contacts privately, without placing passwords or recovery codes in a shared migration checklist.
The Turbify Store Manager documentation index provides a route to catalog and order-management help. Confirm the instructions against the interface and product you actually have. Ask support to clarify anything your account cannot export before setting a cutover date.
Map the pieces that need to keep working
| Dependency | Record | Acceptance check |
|---|---|---|
| Catalog | IDs, SKUs, variants, options, images, prices, stock, compatibility | Representative products retain the correct choices and values |
| Orders | Open and historical orders, totals, fulfilment state, refunds | Staff can find and service orders across the cutover |
| Domain and DNS | Registrar, nameservers, records, responsible administrator | Website and email resolve as intended |
| Mail provider, addresses, routing, sending configuration | Inbound, outbound, and order notifications work | |
| Payments and integrations | Providers, callbacks, tax/shipping rules, inventory feeds | Test checkout, notification, fulfilment, and refund paths |
| URLs and content | Current pages, custom templates, policies, redirects | Old product links reach suitable destinations |
Keep private exports access-controlled and retain only the customer data needed for the move and applicable business obligations. Ask providers how accounts, payment tokens, and subscriptions can be transferred. Do not assume that an exported catalog contains customer passwords or portable payment credentials.
A domain registration, its DNS service, website hosting, and email hosting may have different providers. Changing nameservers can affect all DNS records, including mail. Save a complete current record inventory and agree who will make and verify each change.
Prove a sample import before moving everything
- Keep untouched originals of each supported export and record when it was produced.
- Build a private test destination and import a representative sample: simple products, options, variants, unusual characters, out-of-stock items, and image-heavy pages.
- Compare both counts and meaning. A row count can remain equal while options are attached to the wrong product.
- Test a complete permitted checkout and follow the order through staff processing. Reconcile totals, shipping, tax settings, notifications, and refund behavior.
- Document any custom template logic or integrations that need replacement, then repeat the sample test after repair.
Use the legacy-store migration sheet to record dependencies, sample checks, discrepancies, and sign-off. A successful rehearsal is a prerequisite for scheduling the production move.
Define a cutover and recovery plan
Choose a manageable window and establish how new orders and stock changes will be handled between the first export and the final import. Record a cutoff timestamp, complete a final reconciliation, and assign staff to monitor orders arriving at either system. A backup of yesterday's catalog does not resolve today's pending orders.
Map each changed old URL to the closest appropriate new page. Google's site-move guidance covers URL mapping, redirects, updated links, and post-move monitoring. Keep useful destinations specific; sending every removed product to the homepage loses the customer's context.
Before switching, name the person who can reverse routing, the conditions that trigger recovery, and how orders created on the new system will be reconciled if routing is reversed. Keep the old service available for the agreed verification period, subject to its contract, and test website, mail, payments, and staff workflows after the change.
Close the move only after discrepancies are resolved and access, exports, and support responsibilities are documented. For catalog discovery on the destination, use search evaluation with realistic product queries.