Moving from Khorozhop: directory, addresses, own code
Moving the store from Khorozhop means moving two things: the catalog in machine form and every address already known by search. The catalog goes by download, addresses by a map of correspondence, where a new one stands against each old path. The volume is determined not by the number of products, but by the number of addresses in the index and whether it will be possible to close them with a rule instead of a separate table. The term is 18–35 working days, the amount is named after a free audit.
how many lines will there be in the map of correspondence of addresses
after a free audit
Price
30
Guarantee
days after project sign-off
how many lines will there be in the map of correspondence of addresses
The main figure of the estimate
site map, Search Console export, product feed
Where do we get the list of addresses from?
1,000
Search Console download limit
rows through the interface, more through the API only
18–35
Term of moving
working days from approval of technical specifications
free audit, 2-4 working days
Before the estimate
30
After switching
days we look at scanning errors - included in the work
Free pre-move audit
People leave the storefront with a subscription not because of the subscription price, but because of the limit of possibilities: there is no module, no access to the code, but there is a task. The audit shows how realistic this limit is for you and what the move will cost. Sometimes the answer sounds like "you don't need to move now", and this is also the result of the audit.
What we measure
Directory volume and addressesWe count on the site map and by cross-staff search, we show the discrepancy between the methods. This number becomes the number of rows in the address mapping map.
Path structureHow category and card addresses are built. The main thing depends on this: whether the redirects will be closed by the rule, or whether the table will have to be compiled individually.
Repeat in the site mapHow many entries per unique address. In the stores we measured, we saw not a single repeat for 1,992 addresses, and 7,782 entries for 2,755 unique ones — the volume of work from this changes many times.
Speed to moveFirst server response, full HTML load, and page weight measured BEFORE. Otherwise, after launch, you will have to compare feelings, not numbers.
What exactly are you missing right now?Specific list: integration, pricing logic, catalog structure. The main audit check — some points are closed without moving.
Analytics and Search ConsoleWhat counters are there and whether the rights have been confirmed. Without Search Console, no one, including us, can see the full list of addresses in the index.
What you get
Document with numbers: directory volume, addresses and repeats, speed, HTML weight, analytics status.
The estimate of the number of lines in the map of correspondence of addresses is the main multiplier of the estimate.
Direct conclusion, whether your problem is solved without moving.
Talk for 30-40 minutes on this document.
Timeline: 2-4 business days from when we receive the store address
Why is it free
Because moving from a work window is easy to decide emotionally and expensive to fix. We measure, show the numbers and call the amount once. If the move is not necessary, let's say it directly: this answer is cheaper for us than a project in which the customer will be disappointed in the second month. The document remains with you in any case.
What's next
Next, the cost and term by stages with calendar dates, contract, invoice, act.
Short form: your contact and site URL
Contract, act and 30-day warranty
Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.
Sole proprietor & bank transfer
The contractor is a registered sole proprietor. Payment by invoice with closing documents.
Rights & access — yours
Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.
Client portal instead of email chains
During the project you get access to a portal: contracts, invoices, acts and project status in one place.
European clients
Among our work — projects for Norway, Bulgaria, Moldova and Spain.
Verifiable numbers
Every case in the portfolio comes with a link to a live site and a technical measurement.
Audit first, then pricing
There is no price list on the site intentionally: the scope of the same work differs multiples between clients.
We say "no" when unsure
If the task isn't ours or the deadline is unrealistic — we tell you upfront.
What affects the price
Why two seemingly identical tasks are priced differently
How many addresses are in the indexPrime factor. There will be the same number of lines in the correspondence map and the same number of addresses will have to be checked after switching. This number is not visible from the description of the task - it is measured.
Are redirects closed by the ruleWhen old and new paths are built according to the same logic, redirects are written with several rules. When not, the table is compiled individually, and the difference here is not in percentages, but in times.
How many additions have grown on top of the showcaseThey are the ones who most often keep the store in place. Part of the functionality will have to be recreated — these are separate lines of the estimate, and they should be identified during the audit, and not during the third week of work.
The state of the characteristics in exportFilled out in the same way - spread out by script for the day. Filled with free text for several years - manually compiled and is the most boring estimate line after import.
Number of integrations and feedsEach payment gateway, carrier and export on the marketplace is a separate connection and a separate check on the live order. The feed also needs to be reconciled with what the platform has already accepted.
Language versionsEach language has its own set of addresses and its own branch in the sitemap, i.e. the correspondence map multiplies. In the stores we measured, we regularly found a second language version that is not on the site map at all.
Who it's for
Situations where this service delivers results
Scenario 1 of 4
They rested on the limit of the platform: there is no required function, and no one can make it
The task is formulated, the contractor is found, but there is nowhere to insert the code. Then the move is not about saving money on the subscription, but about making the task complete at all. Checking the limit is simple: write on a sheet the three things you lack and bring this sheet to the audit. If two out of three are covered by the current storefront settings, we'll say so directly.
We'll review your situation in a free audit
Scenario 2 of 4
You calculate the prices more complicated than the shop window can
Wholesale levels, personal discounts under the contract, price according to packaging multiples, separate checkout for FOP and LLC with VAT. Such logic lives in the code, not in the settings: on your own store, it is written once under your rules. This is the most common real reason for moving that we see in briefs.
Scenario 3 of 4
The catalog has grown, but the filter is not collected
The characteristics have been filled in free text for years: "0.5 l", "500 ml" and "500 ml" are three different values. In any download, they will arrive in one column of text. The work of moving here is not to copy lines, but to normalize values - it is after this that the filter starts to filter something.
Scenario 4 of 4
You want the files, database and access to the server to remain with you
Once you move, backups, hosting choices, and PHP version become your responsibility — and your right. This is a plus and a minus at the same time: someone specific will have to administer it. If such a person does not exist and is not planned, it is more honest to stay on the subscription.
What's included
Complete list of work and what you get as a result
We download the catalog in machine form - products, categories, characteristics, photos, descriptions: then a script works with it, not a manager
We normalize the values of the characteristics and make them fields with a fixed list - without this, the filter will be collected on the new store, but it will not filter anything
We make a map of correspondence of addresses: there is a new one against each path that knows how to search
We put 301 from all the addresses that were in the index and run the list completely before the switch, and not selectively after complaints
We take images to your server before turning off the subscription: after turning off the links to the pictures simply stop opening
We're bringing payment, shipping, analytics, and feeds to marketplaces and checking each on live order, not in settings
We close the technical SEO of the new store: CNC, canonical, unique title, site map without repetitions
Moving text and meta descriptions that are already driving traffic: rewriting them on the move is an added risk, not an improvement
We install GA4 and Tag Manager with cart and purchase events, confirm rights in Search Console — so that there is something to measure after the move
We write a switching plan: what we do on the night of the transition, what we check in the morning, what we look for in the first 30 days
We transfer access, written instructions for your processes and go through administration together with your manager
Terms of work: 50% advance payment, two rounds of edits at the design stage, warranty period of 30 calendar days
When this service isn't right
What's not included — so there are no surprises at delivery
Order history as an accounting archive: we will download it, but we will not attempt to reproduce it in the new system
Promises of items and traffic after the move - they are not given by anyone who works honestly
We count the catalog and addresses using two methods, we take away the machine export of goods, characteristics and photos, we remove the list of integrations. The output is the numbers by which the estimate is calculated.
2
Map of correspondence of addresses
3-6 working days
We combine the addresses from the site map, Search Console export and product feed into one list, remove repetitions and decide where the redirect is made as a rule and where as a separate line.
3
Assembling a store on a technical domain
6-12 working days
Tree of categories, card, basket, checkout, roles in admin. The store lives in parallel with the work, so everything that breaks does not break on the customers.
4
Catalog and specifications
3-7 working days
We fill the goods, reduce the values of the characteristics to one form, collect a filter from them, compare the number of cards before and after filling.
5
Integrations, analytics, feeds
2-4 working days
Payment and shipping with end-to-end order flow, GA4 and Tag Manager with cart events, feeds to marketplaces, rights to Search Console.
6
Switching and the first 30 days
2 working days
Running the entire list of redirects to the transition, changing the direction of the domain in the evening, checking the response codes in the morning, then a month of watching for crawl errors.
Did not find your case?
Describe how it works on your side — we will tell you whether “Transferring the store from Khorozhop to its own platform” fits and what it means in your situation. No brief and no call: one question, one answer.
Cases
Tasks and results in numbers — all metrics measured by us
a wholesale store of cosmetics for the beauty industry — our technical measurement of an operating store, we did not perform the migration from Khorozhop
Task
To understand from which site map to take addresses, when there are two of them in the store and they do not match.
Solution
Both maps were analyzed, entries were reduced to unique addresses and compared with language branches.
Result
Canonical map — 4,167 addresses: 3,947 products, 166 brands, 47 categories. In parallel, the live old map gives 7,782 records, of which only 2,755 are unique and about 2,706 are marketable — it is both duplicated and incomplete. There is no address of the second language version in the maps, although bilingualism is declared in the hreflang. Measured on 07/31/2026.
a professional cosmetics store with a catalog of more than 5,000 items is our technical dimension of an operating store
Task
Compute a directory where a sitemap is unsuitable as a source of addresses.
Solution
We calculated the full-time store search page by page: 55 pages with 100 items and 61 for the last one.
Result
5,561 products in the live catalog. At the same time, the site map gives HTTP 200 with a body of 0 bytes, that is, the list of addresses cannot be obtained from it at all - the correspondence map would have to be collected from the Search Console and the feed. TTFB 801.2 ms at 153.8 KB HTML, no analytics counter on the site. Measured on 07/31/2026.
The B2B spare parts catalog for industrial sewing machines is our technical dimension of the existing store
Task
Show what a store looks like, in which the move does not create problems with addresses.
Solution
Checked the sitemap in its entirety and compared it with language versions and hreflang.
Result
1,992 addresses — 1,848 product cards and 138 categories, no duplicates. The compliance map for such a store is two thousand rows, not tens of thousands. TTFB 388.1 ms at 120.2 KB HTML. Defect found: The code still has a gtag connected to the Universal Analytics config that Google disabled on July 1, 2023, and no GA4 property - analytics has been dead for three years. Measured on 07/31/2026.
a furniture store for the Spanish market is our technical dimension of an operating store
Task
Verify that two independent methods of counting the catalog before the move converge.
Solution
We counted the products according to the product sub-map of the site and separately by regular search of the store.
Result
76 goods by both methods, the discrepancy is zero - the case when the figure of the estimate can be trusted right away. In total, the map contains 88 addresses: 76 products, a category, ten information pages and the main page. TTFB 348.2 ms. Measured on 07/31/2026.
Technologies & integrations
What we build on and what it connects to
Stack
OpenCart 4.x is a branch under development; set as default so as not to migrate a second time after a year
OpenCart 3.x — when a critical module has an assembly of only three; we fix the version in the TK before the start
PHP and MySQL are a fair boundary: you or your hosting will have to update them after the transfer
nginx - redirects live at the server level, not in the store code, so they survive updates
HTTP/2, HTTPS + HSTS
Google Search Console is the only source of a real list of addresses in the index; without access the list will be incomplete
Integrations
LiqPay
WayForPay
Privat24
monobank
non-cash settlement
postpaid
Nova Poshta
Ukrposhta
Meest Express
XML feeds to marketplaces
Google Tag Manager
GA4
Google Ads
Google Search Console
eSputnik
What changes when the store becomes yours
How this option differs from the alternative
Showcase with subscriptionOur approach
A new feature that is not in the boxwait in the platform roadmap or go around to the sidewritten according to your rules, the term depends on the performer
Files and databaseat the platform, within the limits of what it allows to unloadyou have: the backup is taken whenever you want
Address structuregiven by the platformchanges for SEO tasks
Update and securityplatform does, and that's a real advantageyour zone: PHP, Core, Modules, Backups
Fixed costspredictable subscription with no surpriseshosting, domain and work of the developer under the tasks
What we need from you
We can't start without this — best to prepare in advance
1The address of the current store — the audit begins with it.
2Access to the admin to download the catalog or ready download of products and characteristics.
3Access to the Search Console, if the rights have already been confirmed: without it, the list of addresses in the index will be incomplete.
4List what you are missing right now - in specific items, not "we want our site".
5Access to DNS and domain: the switch is done right there.
6One person with the right to make decisions about the directory structure and confirm the switching window.
If something is missing — let us know, we'll help you gather it or do it as a separate task.
FAQ
Most frequently asked questions — with concrete answers
The store is open, the sales are going - why go anywhere at all?
Often it is not necessary, and we say so at the audit. The move is justified when there is a specific task that the storefront does not close: its own price logic, non-standard data exchange, access to the code. If the reason sounds like "bored" or "I want my own", the audit usually shows that it is cheaper to finish what is there. We write such a conclusion in the document in direct text: a project in which the customer does not understand what he paid for after a month is more expensive to us than a lost deal.
Where will you get a list of addresses if there is no access to the server?
From three sources, each individually incomplete. A sitemap provides structure, but can be outdated or repetitive. Search Console gives you what search really knows — with a twist: the front-end download is truncated at 1,000 rows, so for large directories we pull data through the API. The third source is a product feed for marketplaces: it contains the addresses of cards that often bring the most conversions. These three lists are combined into one, duplicates are removed, and a matching map is obtained.
Can addresses be stored one-to-one?
This is the best-case scenario, and it's more realistic than it seems: if the path structure allows for the same addresses to be reproduced, no redirects are needed at all. When the structure is different, most of the addresses are closed by several rules, and the individual table remains for exceptions — moved categories, merged cards, old promotional pages. Which of these is your case can already be seen on the audit, before the contract.
When can I unsubscribe on the old platform?
Our recommendation is no earlier than 30 days after switching, and this is not caution for caution's sake. As long as the subscription is active, you have a place to roll back: the direction of the domain has been returned — and the old storefront is working. Plus, images and data remain available if something was not delivered to the new store. A month's subscription is cheaper than one evening when you have nowhere to go.
What happens to product photos?
They must be physically picked up before the subscription is turned off. Images on such a platform are distributed by it, and links to them live exactly as long as your account is alive: after disabling the card, the new store will remain without images, if the files are not uploaded to you. We take them in batches together with the catalog and compare the number of files with the number of cards - it is on this reconciliation that products that have never had a photo come out.
Will the characteristics themselves become a filter on the new store?
No, and this is the most underrated part of moving. In the export, the characteristics come in text: "0.5 l", "500 ml" and "500 ml" - three different values for the machine, although for the buyer it is one. The filter needs a fixed list field, so the values are first reduced to a single form and then made into a field. A fair limit: the filter does not add demand for a product that is not being searched for, and in a catalog with several dozen items, the profit from it is minimal - there, a clear structure of categories gives more.
How long will the store be closed?
Downtime is measured in minutes: the new store is assembled in parallel on the technical domain, filled and tested, and on the day of the transition, only the direction of the domain changes. The risk is not in idle time, but in redirects - that's why we run the list completely before the switch, and not selectively after. We switch in the evening, in the morning we check the answer codes on the entire list.
And if it is impossible to transfer some of the improvements?
Then you will hear it at the audit, before the contract. Most often, we are talking about mechanisms that exist only inside the platform: their work has to be reproduced anew, and these are separate lines of the estimate with a separate deadline. Learning about such a module in the middle of the project is the worst-case scenario for both parties, so we go through the list of your improvements item by item at the very beginning.
What will happen to the items and how long does it all last?
Part of the traffic sinks in the first weeks - this happens with any change of addresses, and it would be untrue to promise otherwise. Our zone: close each address from the index with redirects, save the structure and texts, give the site map without repetitions and watch scanning errors for a month. A separate fair limit: after cleaning duplicates, the number of pages in the index may drop - this is an expected course of events, not a crash. The period of relocation is 18-35 working days from the approval of TK, of which audit and export 2-4 days, compliance map 3-6, assembly 6-12, catalog 3-7, integrations 2-4, switching 2.
Give the address of the store and a sheet with the three things you currently lack. In 2-4 working days, we will return with a document: how many addresses do you have, how many of them are repeats, what is the rule for moving and whether you need to move at all.
There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.