Moving from Shopify to your own store

The reasons we hear more often than others are: a monthly bill where the tariff, app subscriptions and transaction fees add up to a significant sum; the need to accept payment by Ukrainian services and issue documents for sole proprietorships and LLCs; the desire to have access to the code and database. We do not persuade anyone to move. At the audit, we calculate how much the move itself costs and what will have to be reproduced, and you make the comparison with your account.

Mostly not, and this is the main reason why moving from here is cheaper than moving from a self-written engine. In Shopify, the same card is available in two paths - /products/<handle> and /collections/<collection>/products/<handle>, with canonical standing for short. Therefore, the transition is described by three rules at the server level: collection per category, long path of the card to the new product address, short path to the same place. We list only exceptions one by one: pages whose addresses have changed hands, and promotional collections for campaigns. We take the list from the site map and Search Console and fill it with response codes even before switching.

Moved as options inside the card or as separate cards - depending on how they are searched: shoe size people enter in the search, the shade of accessories - not. The technical trap here is the same: in the download, the first line of the product carries the name and description, and the following lines of the same product are variants with an empty Title field. Importing "as is" turns them into individual goods without names, and prices and balances creep up. Therefore, first we collect lines in the model by handle, then we divide them into options, and at the output we compare the number of options before and after each collection.

The payment flow is being rebuilt: Shopify Payments is not available in Ukraine. The place of online payment is occupied by LiqPay, WayForPay or monobank, next to it we put post-payment and a non-cash account for FOPs and LLCs with and without VAT. You conclude the contracts, the keys are issued to you - the contractor does not keep them. On our side, setup, end-to-end running of the real order by each method and display of payment conditions on the site. How many methods are really needed is a question of your segment: in a narrow B2B it can be one invoice with VAT, and ten logos in the footer will not add anything.

Divide into three piles. The first is what is standard in the new engine: discounts, coupons, bundled products, basic filters. The second is what is covered by the module: reviews, feeds on sites, advanced catalog search. The third is something that has no analogue: specific subscriptions, narrow calculators, external services with their own office. For the third time, we count the additions separately, and it happens that the amount turns out to be more than the years of subscription - then we say so, and not sell the move. Separately: customer subscriptions and saved payment data are not transferred in principle, they remain with the payment provider.

Not on the day of switching is our direct recommendation, and it saves the most nerves. Keep Shopify alive for at least 30 days after the move and don't cancel early: after the paid period ends, the admin is closed and there's no way to re-extract the catalog export, order list or app settings. During these 30 days, we go through scanning errors in Search Console and select addresses that did not fall into the rule. When the list is clean, then cancel.

Will save, but not automatically. Language versions are redesigned: own addresses, hreflang with x-default, separate delivery terms and currency settings. The fair boundary here is this: the translated storefront is not yet an entry to the market - local payment, local delivery and local prices are required, the site closes only the first step. In the two stores we measured, this is done differently: the Spanish-speaking furniture store lives in one language with the correct hreflang, the Bulgarian cosmetic store keeps three versions of bg/en/ru. And it is in the second that the sitemap and robots.txt give an empty body — language branches for search are simply not declared.

18-35 business days from TOR approval, the six-stage breakdown is above: audit 2-4 days, export and variant parsing 2-4, assembly with payment flow 7-14, redirects 2-4, catalog migration and reconciliation 3-6, switching and control 2-3. There is no price on the page on purpose, and this is not a way to avoid the answer: the amount is determined by your store - the number of options, the list of applications and how many calculation methods will have to be reassembled. To calculate this, we do a free audit for 2-4 working days, and already by its numbers we call the cost and term by stages with dates.

We work officially: contract, invoice, act of completed works, including with customers from the EU. Advance payment of 50% at the start, the rest — after acceptance before switching. Two rounds of edits at the design stage are included in the cost if they are within the approved TOR. Thirty calendar days after acceptance, we correct errors free of charge on our part - this is the warranty period according to the contract, and it does not cover new additions and the consequences of independent changes in the code. Calculation in euros, hryvnias at the rate of the NBU on the day of the account, the amount named after the audit is valid for 14 days.