Moved the store off InSales to our own engine — full control over the site, data, and speed, with no platform limits or tariffs.
IWANT — store migration from InSales to a custom engine
IWANT is our own fashion brand and online store. It started on InSales, but the platform capped us with tariffs, limits, and paid add-ons. We moved it to our own engine: kept the SEO and order history, gained full control over the site and data, and cut the cost of ownership.
Challenge
On InSales the brand hit the ceiling of the platform: needed features only through paid apps, and no full control over code, data, or speed. We needed a custom engine — without losing SEO, order history, or day-to-day store operations.
What we built
Kept the SEO and history: migrated the catalog, 3,123 orders (2016→2026), and 7,636 pages with redirects — no loss of search rankings.
Built features you pay extra for on InSales: abandoned-cart and win-back emails, gift cards, cashback, reviews, back-in-stock alerts, personal recommendations.
Added the IRIS AI stylist — it helps shoppers put an outfit together right on the site.
Built an easy admin: products, content, promos, and SEO are managed in-house, without a developer.
Built our own analytics and a cookieless, first-party traffic tracker: cart→order funnel, sources and devices — no cookies, no external counters (152-FZ).
The whole catalog and content migrated with full 301-redirect coverage.
Lighthouse on mobile: SEO 100, Best Practices 100, zero CLS.
Order history 2016→2026 migrated, powering win-back and recommendations.
Own engine on a VPS vs InSales tariffs of 2,300–10,400 ₽/mo plus paid apps.
Migration: technical details
SEO preserved
7,636 pages migrated with complete 301-redirect coverage — indexing and rankings kept.
Custom ETL
Our own parser for InSales (UTF-16) exports: products, categories, and 3,123 orders moved into PostgreSQL.
Architecture
Next.js 15 on RSC and Server Actions, an idempotent email queue, a blue-green cutover with no downtime.
Inside the project
Next.js 15 (RSC, Server Actions), TypeScript, Tailwind, Prisma + PostgreSQL, next-intl (RU/EN), YooKassa, CDEK, the IRIS AI stylist on GigaChat, self-hosted on a VPS with a CDN.
- Migration from InSales to a custom Next.js engine
- Catalog, 3,123 orders, and SEO structure migrated (7,636 pages, 301 redirects)
- Retention emails, server-side cart, gift cards, cashback wallet, reviews, back-in-stock
- IRIS AI stylist on GigaChat (152-FZ)
- Full admin CMS: products, variants, content, SEO
- SEO/GEO: sitemap, Schema.org, llms.txt, OG, YML feed; RU/EN
- Self-hosted on a VPS with a CDN
- First-party analytics + cookieless traffic tracking (152-FZ)
Migration from InSales to a custom engine
We migrated our own fashion store from InSales to our own engine: kept the SEO, moved the order history, and built in features you normally pay extra for on a platform.
TECHNOLOGIES AND SOLUTIONS
- Next.js 15
- RSC
- Prisma
- PostgreSQL
- ЮKassa
- СДЭК
- GigaChat
- SEO/GEO
- Next.js 15
- Prisma
- PostgreSQL
- SEO/GEO
We migrated our own store — so we know your migration from the inside
We do not just build e-commerce — we moved our own store off a platform onto a custom engine. We know the cost of every step: keep the SEO, do not lose order history, do not stop sales.
We do the ownership math honestly: an InSales tariff plus paid apps versus a custom engine on a VPS under 1,000 ₽/mo. Over a year the gap is real.
It fits brands on InSales, 1C, or Shopify, and sellers who live only on marketplaces and want an owned sales channel.
A free 3-minute video review of your site
Send a link and I will record a personal review: where you lose on speed, conversion, and SEO, and what a move to your own engine would change. No call, within 48 hours.
Want a similar store for your brand?
We can break down the owned sales channel that fits your catalog, content workflow, and order flow.