Design + content migration
Recreate the agreed layouts, typography and interactions as Astro components, and move your content. We review desktop and mobile reference pages together; design changes are listed separately.
WordPress · Bitrix · Legacy websites
WordPress to Astro migration
ERPixel migrates WordPress, Bitrix and legacy websites to Astro: content, page templates, URLs and agreed functionality. Keep your existing design or choose a redesign. Send your website URL to receive a migration proposal by email after our review.
A reviewed scope and estimate. No instant price generated from a URL.
Start with your website
A clear proposal, sent to your inbox
Send us the website you want to migrate. We review its public pages and email you a scoped proposal, or questions if we need more information.
- Templates and sections to rebuild
- Content and media to migrate
- Functions, editing and integrations
- Estimate, assumptions and proposed delivery stages
No account or payment is needed to request a proposal. Please do not include credentials or private customer data.
Website migration to Astro
Keep what works. Rebuild what holds you back.
A migration to Astro rebuilds your public website in a modern component-based framework. We can transfer content into a new design, or recreate the existing design and transfer the content together. WordPress plugins, Bitrix modules and business workflows are assessed separately: they do not automatically become Astro features. We agree the editing system, integrations and launch plan before development.
Choose the right scope
Your current design, or a fresh start?
The proposal makes the difference explicit. You can migrate selected sections first rather than replace everything at once.
Content migration + new design
Move and clean the content, then place it into approved new templates. Design selection or custom design is a separate line in the proposal. We use licensed templates and reusable blocks where they fit.
A staged migration
Start with the homepage and one service or product template. Approve the approach on staging before migrating the remaining sections or blog. Keep existing systems where replacement has no clear benefit.
Migration scope
Estimate templates and content separately
Ten pages sharing one layout are different from ten unique designs. We separate template development, content import and functional work so you can see what drives the estimate.
Homepage
Rebuild the main page, navigation entry points, responsive sections and agreed forms. A dedicated eCommerce homepage is estimated as its own template when it has a different structure.
Service pages
Build an approved service template and migrate the pages that use it. Unique layouts, calculators or interactive elements are scoped separately.
About, Contact and supporting pages
Transfer company information, contact details, legal pages and other agreed content. Reconnect contact forms, consent handling and analytics where included in scope.
Product pages
Rebuild product presentation, images, specifications and variants. Prices, stock, accounts, cart and checkout require a working commerce backend and a separate integration scope.
Category pages and store homepage
Migrate category structure, product listings and store landing pages. Filters, sorting, search, pagination and live availability are explicitly estimated.
Bulk blog migration
Import agreed posts, images, authors, categories and metadata into shared article templates. Clean shortcodes and old builder markup, map URLs and check the import. Individual editorial rewrites are separate.
From URL to launch
How your migration works
Approve the scope before development and the staging site before launch. Timing depends on unique templates, content volume, editing requirements and integrations.
- 01
Send your website and email
Tell us whether to keep the design or move only the content, which sections matter, and which functions must continue working. Do not send passwords through the form.
- 02
Review and written proposal
We review public pages and clarify missing information by email. Your proposal separates template work, content import, CMS setup, integrations, QA, launch and optional improvements, with price assumptions and a proposed schedule.
- 03
Agree access and a reference template
After agreeing the scope, arrange secure access and backups. We implement the homepage and a representative service, article or product page on staging for your review.
- 04
Migrate the approved sections
Roll out the accepted templates, import content and media, reconnect agreed functions, and map old URLs to their new destinations.
- 05
Check and approve
Review responsive layouts, forms, links, content samples and migration totals. We check metadata, redirects, canonical URLs and structured data. Fixing migration defects is included in the agreed acceptance scope.
- 06
Launch, handover and improvements
Agree a content freeze and final import, keep a rollback copy, then launch and check the public site. Receive editing and deployment instructions. Redesign refinements, new features and ongoing support follow a separately approved scope.
Why Astro?
A lean foundation for your next website
Astro is a strong option for content-rich websites and custom storefronts. The right architecture still depends on your editing and business requirements.
Fast pages by design
Pre-rendered HTML and selective JavaScript can reduce browser work. We check the delivered pages: large media, trackers and third-party tools still affect performance.
Design without a bulky theme
Build a polished, responsive interface from reusable components. Astro provides flexibility; good visual design comes from the layouts and details we implement.
Fewer runtime dependencies
Static public pages can run without a public WordPress/PHP database stack. Forms, CMS access, dependencies and deployments still need security and maintenance; no website is unbreakable.
Ready for integrations
Connect a CMS, CRM, ERP or commerce API through a planned integration. Dynamic data, authentication and backend rules require their own design and testing.
Lightweight hosting options
Static output can be served from a CDN without a full CMS runtime. Actual storage and hosting costs depend on media, page count, traffic and dynamic services.
Reusable templates and blocks
Reuse approved components across pages and use suitable licensed templates. New pages become easier to produce while each page keeps a clear purpose.
Why ERPixel?
Migration experience you can inspect
Our WordPress-to-Astro experience includes erpixel.com, erpixel.pl, pmoffice.by and alexanderkoltsov.by. We work quickly by approving representative templates first, reusing components and importing repeated content in batches. We agree delivery dates after reviewing your site; we do not promise an arbitrary turnaround.
ERPixel.com
Our own company website: WordPress-to-Astro migration experience.
Visit ERPixel.comERPixel.pl
WordPress-to-Astro project from our migration experience.
Visit ERPixel.plPMOffice.by
WordPress-to-Astro project from our migration experience.
Visit PMOffice.byAlexanderKoltsov.by
WordPress-to-Astro project from our migration experience.
Visit AlexanderKoltsov.byBefore you migrate
WordPress to Astro migration: questions answered
Can you migrate Bitrix or another legacy website to Astro?
Yes. We offer Bitrix-to-Astro and other legacy website migrations after reviewing the content, templates and functionality. Our named migration examples are WordPress projects. Bitrix business logic, customer accounts and commerce modules need a separate assessment.
Can you preserve my design, or migrate content only?
Both are available. We can recreate the agreed existing design, or migrate your content into a new approved design. The proposal states which templates are included and whether design work is additional.
Will I still be able to edit the website?
Yes, with an agreed editing workflow. Options include a headless CMS, retaining WordPress as a content backend, or file-based content with managed updates. We choose the editing approach with your team before estimating the implementation.
How much does a WordPress to Astro migration cost?
We quote after reviewing the site. Cost depends on unique templates, content volume and quality, design changes, the editing system, functionality, integrations and launch requirements. The email proposal separates those items and identifies assumptions and exclusions. Submitting a URL does not generate an instant fixed price.
Can you migrate a WooCommerce or Bitrix store?
We can rebuild the public storefront in Astro. Product and category pages are only part of the work: cart, checkout, payments, taxes, stock, customer accounts and order history need an agreed commerce backend and migration plan. We may recommend retaining the current engine.
Can you preserve SEO and make the site readable by AI search?
We retain useful URLs where possible, map redirects, transfer metadata and check canonicals, internal links, sitemap entries and appropriate structured data. Key content remains available in HTML. These steps support search access and interpretation but cannot guarantee rankings, indexing or AI citations.
Are post-migration changes included?
Corrections needed to meet the agreed migration acceptance criteria are included. New layouts, rewrites, conversion experiments, extra integrations and other enhancements are estimated separately. The proposal states the review process and support boundaries.
Plan your migration with ERPixel
Request your migration proposal or contact our team. If the project also changes your business systems, explore our Odoo integration services.