Contents 13
What a migration actually includes
Horoshop can import products from supported files, but the category tree, characteristics, variants and storefront need preparation. Complex databases can require developer work. A product transfer does not copy every feature of the old platform.
List the catalog, content, integrations, URL behavior and operational processes you need to keep. For each item, agree the source, destination and acceptance check. Separate the import from design, checkout setup and the final switch.
- Check a representative export before estimating the work.
- Assign an owner for each integration and data source.
- Agree what remains in the old system or archive.
Prepare the catalog before exporting
Record product identifiers, categories, variants, images, prices and availability. Keep a sample that includes the difficult products, not only simple items. Compare the source with the trial import before transferring the full catalog.
Confirm which data is authoritative and how prices and stock will update after launch. Resolve missing fields and duplicate identifiers in the agreed scope. A successful file upload is not evidence that every product, filter or variant is correct.
- Check parent/variant relationships and characteristic units.
- Confirm image access and category mapping.
- Plan the final data update close to the switch.
Tilda to Horoshop: catalog and page content are separate
Tilda supports CSV and YML for its Product Catalog. Check whether the products you need are in that catalog or only displayed in page blocks. Export the catalog and inspect the fields against the destination import requirements.
Product import does not reproduce Tilda page design, custom blocks or scripts. List the content and functions that need rebuilding, map the affected URLs and test the result. Confirm variants, images and the order flow in the trial store.
- Use a trial import before the full catalog.
- Separate catalog data from page content and custom code.
- Map the old product and content URLs.
Wix to Horoshop: check the export limits
Wix Stores offers CSV export for physical products; its documented product export does not support digital products. The new catalog supports up to 5,000 CSV rows. Rows are not necessarily individual products, because variant data can use additional rows.
Check which catalog version your store uses and whether the exported columns contain the required information. Wix pages, app behavior and customer or order data need their own transfer plan. Do not promise that a product CSV recreates the complete store.
- Compare row counts with products and variants.
- Inspect the actual export rather than relying on a generic checklist.
- Agree page content, apps and historical data separately.
WooCommerce to Horoshop: products are not plugins
WooCommerce has a built-in product CSV importer and exporter. Check the exported types, attributes, variation relationships and image references against the destination. Data from plugins or custom fields may require a separate export and mapping.
List the functions provided by plugins: pricing, stock, payment, delivery, discounts and other workflows. Confirm the destination equivalent or agree additional work. A product transfer does not move WordPress code, theme behavior or every plugin feature.
- Verify SKU and parent/variant relationships on a trial import.
- Describe the plugin functions needed after migration.
- Accept integrations separately from catalog data.
Prom to Horoshop: distinguish your domain from the marketplace
Horoshop describes support for Prom product export files. Check the actual export from your account, including categories, modifications, images and availability. Format support still requires a sample import and data acceptance.
SEO work depends on who controls the old domain and URLs. Do not promise redirects on marketplace-owned addresses without a confirmed way to configure them. If you keep your own domain, plan the URL map and DNS switch; if the domain changes, agree redirect hosting separately.
- Separate your own domain from marketplace pages.
- Confirm which old addresses you can redirect.
- Test payments, delivery and product-feed updates.
Reduce SEO migration risks before switching
Collect the old URLs, important landing pages and Search Console baseline. Where addresses change, prepare permanent 301 or 308 redirects to the relevant final pages. Do not redirect everything to the home page or a temporary staging domain.
Check canonical URLs, internal links and real language versions. Remove staging noindex only from pages meant for indexing. After launch, check sitemap entries, responses and indexing. Google warns that rankings can fluctuate; correct technical work is not a promise of unchanged traffic.
- Keep matching redirects; Google recommends at least a year for changed URLs.
- Monitor important organic landing pages, errors and orders.
- Keep the old domain or hosting if redirects still depend on it.
Separate platform import from the implementation budget
At the check date, Horoshop lists UAH 4,200 for its migration service, or no import charge with an annual Standard subscription or higher. Confirm the current terms and included data with the platform. This is not the price of a complete UPLIFY implementation.
Our scope depends on export quality, catalog structure, design, integrations, SEO mapping and launch work. See the current development offer for packages and inclusions. Agree the migration estimate after reviewing a data sample, with paid platform plans and third-party tools identified separately.
- Separate import from content preparation and integrations.
- Identify who fixes source data and accepts the result.
- Agree the final scope before payment.
Current development packages →
Estimate the schedule from the actual dependencies
SKU count alone does not determine the work. A clean large catalog may be simpler than a small store with complex variants, custom URLs and integrations. Agree timing after the trial import and dependency list, not as a universal two- or three-day promise.
Include preparation, trial import, catalog acceptance, integrations, SEO mapping, the final data update and the switch. Leave time for post-launch monitoring. Access, materials and third-party dependencies affect the schedule.
- Assign an owner and acceptance criterion to each stage.
- Agree a switching window and rollback plan.
- Do not confuse import time with the complete launch.
Customers and order history need explicit scope
Horoshop describes customer-data transfer as a separate option when a suitable export is available. Confirm the mechanism, fields and cost for historical orders in your specific project. You may still need a protected archive of the old system after the catalog moves.
Minimize personal data, restrict access and transfer files through an agreed protected channel. Confirm the purpose, fields and retention with the data owner. Legal grounds and marketing communications require separate assessment; importing data is not permission to send campaigns or a guarantee that passwords transfer.
- Record fields, duplicates and a control sample.
- Check order statuses, returns and stock separately.
- Keep the agreed archive private.
Frequently asked questions
Can a store migrate without losing SEO?
A matching URL map, permanent redirects and indexing checks can reduce risk. They cannot guarantee unchanged rankings or traffic: Google warns about fluctuations during a move. Save the baseline before switching and monitor important landing pages, errors and orders afterward.
How much does migration to Horoshop cost?
Platform terms and UPLIFY work are separate. At the check date, Horoshop lists UAH 4,200 or no import charge with an annual Standard plan or higher. Catalog preparation, design, integrations and the SEO plan depend on the agreed scope. Check the current development offer and confirm platform terms.
What format should I export from Tilda?
Tilda Product Catalog supports CSV and YML. Check that the required products are in the catalog, not only in page blocks. Map variants, characteristics and images; agree content and URLs separately. Product import does not reproduce Tilda page design.
Does order history transfer automatically?
Do not assume a universal import. Confirm the export, transfer mechanism, fields and cost for your CMS. Customer data is also separate work. If needed, keep a protected old-system archive with agreed access, data minimization and sample checks.
Can the old store keep running until launch?
Yes, with a final update of prices, stock and orders close to the switch and a plan to prevent duplicates. Test staging without indexing and point redirects to the final domain. Keep old-domain hosting where it is still required for redirects.
Further reading
- Horoshop subscription and implementation costs
- Horoshop or Prom: store and marketplace
- Horoshop development scope and packages
Agree a migration plan for your store
Tell us your current platform, catalog and required integrations. We will agree the transfer scope and launch checks.