No account needed to start. Review before you send.
Grigora
Your next website. One question at a time.
Tell us where you’re starting and what you’d like to bring. We’ll help you plan the move.
Start from any platform
Keep your answers as you go
Review before you send
A few simple questions. No account needed.
A new home for your content. A clear path to get there.
Moving platforms is a series of decisions. Here’s what to expect from the first connection to your next launch.
1
Choose your platform
Tell us where your website lives today. Choose a familiar name or select Other platform for a custom-built site.
2
Plan your move
Connect your content source or share your website with our team. Map out the pages, posts and features you want to bring.
3
Bring it into Grigora
Follow your migration plan, organize your content and shape the design of your new website.
4
Review, connect and publish
Check your content, links and mobile pages. Connect your existing domain when you’re ready to launch.
What is website migration?
A website migration moves your online presence from its current setup to a new home. The content is one part of the job. Your design, domain, navigation and business tools make the move complete.
Move the website your visitors actually use
A website is more than the pages in its main menu. A customer might arrive through a bookmarked article, a product shared in a message, a campaign link or a downloaded guide. Start your migration plan with those real entry points. Record the content people come for and the actions you want them to take when they get there.
When you migrate to Grigora, use that inventory to decide how your new website should work. Keep familiar information easy to find, bring valuable content into the new structure and give each important visitor journey a clear destination.
Separate the move from the opportunity to improve
Switching platforms can also be a chance to simplify a crowded menu, refresh an old design or make publishing easier for your team. Write down those improvements separately from the content you need to retain. That makes the project easier to review and prevents an attractive redesign from hiding a missing service page or contact route.
You can keep your existing brand and domain while changing the platform behind them. You can also plan a broader refresh. The right scope depends on what your website does today and what you want it to do next.
Choose the kind of website move you need.
Moving a blog, changing a website builder and launching under a new domain involve different decisions. Identify what is changing before choosing the migration path.
Switch your website builder
Move from a platform such as Wix, Squarespace, Webflow or Framer while keeping the purpose of your website. Inventory your pages, recreate the visitor journeys and choose how the content will fit into Grigora. A builder switch is also a useful moment to review your mobile navigation and remove duplicated pages.
Move your blog or CMS
Treat posts, categories, authors and related content as a connected publishing system. Decide which material belongs in the new site and how editors will maintain it. Keep track of publication dates, embedded media and links between articles so an archive remains useful after the move.
Redesign while migrating
Keep a record of the current site before changing its appearance. Use that reference to separate intentional improvements from accidental omissions. Approve a representative service page, article and contact journey first, then apply the design consistently across the rest of the website.
Change your domain as well
A new domain adds a separate layer to the project. Plan ownership, DNS, email records and the destinations of old links alongside the platform change. Agree which domain will be primary and who is responsible for maintaining access to the old one after launch.
Before you migrate, gather the essentials.
A small amount of preparation makes a large website easier to move. Collect these materials in one shared place so your team can answer questions without searching old accounts or messages.
A complete website inventory
List your main pages, landing pages, blog archive, resource downloads and any content that lives outside the main navigation. Mark the owner of each section and decide whether it should be kept, updated, combined or retired. Include pages used in ads and emails, even if they receive little organic traffic.
Access to the right accounts
Identify who controls your website platform, domain registration, DNS, analytics and embedded business tools. Prepare the export files or source permissions required by your chosen path. Enter credentials only in the appropriate authenticated workflow, and keep passwords and API keys out of public forms and shared planning documents.
Your brand and original assets
Gather the logo, brand colors, fonts, image originals, videos and documents you want to use again. Keep a record of image rights and licenses. The original files are often more useful than downloading small, compressed copies from the live website.
A clear definition of ready
Name the person who will approve the new website and write down the checks they expect. Include the pages that must be present, forms that must work and content that needs specialist review. A shared acceptance checklist gives the project a concrete finish line.
A website migration plan, from first review to launch.
Organize the work into phases rather than moving everything at once. Each phase should leave you with something specific to review before you continue.
Phase 1
Discover and prioritize
Review the current website with the people who maintain it. Identify valuable content, essential tools and the reasons for switching. Put the most important customer journeys at the top of the plan and record the pages or features that can be improved after launch.
Phase 2
Prepare the destination
Choose the Grigora website that will receive your content. Set the page structure, settle the visual direction and decide how repeatable content such as articles or listings should be organized. Agree names for collections and fields before bringing a large archive into them.
Phase 3
Move and assemble
Follow your source-specific migration path, bring over the planned content and connect it to the new pages. Keep a simple issue list as you work. When a shared component changes, check the pages that depend on it rather than reviewing only the page you are currently editing.
Phase 4
Approve the website
Review a representative set of pages on desktop and mobile, then check the full content inventory. Ask someone unfamiliar with the build to try the main tasks. Fix missing destinations, confusing labels and submission problems before scheduling the domain change.
Phase 5
Launch and follow through
Connect the domain when the destination is ready and the relevant account owners are available. Recheck the live visitor journeys, record any launch issues and assign someone to monitor enquiries and content updates. Keep the previous website and backups available while you verify the transition.
Bring the details that make it yours.
From your most-read blog post to the domain people know you by. Build your migration plan around the content and connections that matter to your business.
Website migration planning checklist
Your website
What to expect
Before you publish
Pages and text
Plan your content
Map the pages you want to bring over, organize your content in Grigora and connect it to your new layouts.
Blog posts and collections
Keep publishing
Plan for your posts, categories, authors and collections so your content stays organized in its new home.
Images and media
Bring your media
Gather the images and files you want to use. Review image quality, embeds, file links and alt text on the new site.
Navigation and links
Reconnect your pages
Map your menus and key journeys. Make sure internal links take visitors to the right place after the move.
SEO titles and descriptions
Carry details forward
Review and set the titles, descriptions and headings that help people find and understand your pages.
URLs and redirects
Plan your paths
Keep important paths where possible and create redirects for URLs that change.
Forms and integrations
Connect your tools
Set up your forms and third-party connections, then test the full experience on your new website.
Design and layouts
Make it yours
Recreate a familiar layout or take the opportunity to start fresh with Grigora’s templates, visual editing and AI tools.
Domain and DNS
Keep your address
Connect your existing domain when your website is ready. Preserve the DNS records used by your email and other services.
Your migration plan brings these steps together. Review the new website before you connect your domain, and keep a backup of your original content.
Website migration guides for your current platform.
Explore detailed paths from WordPress, Wix, Squarespace, Shopify, Webflow and more. Start with the content and customer journeys that make your website useful.
Migrate WordPress to Grigora
Start with the distinction between editorial content and the WordPress presentation around it. Posts, pages, taxonomies, themes and plugins can play very different roles in the finished website. Map the content you want to retain and the behaviors you want your new site to provide.
Prepare your move
Inventory your posts, categories, authors and media. Note any page-builder sections, shortcodes, custom post types or plugin-driven content so they are reviewed as part of the plan.
Review your new website
Sample both recent and older articles. Check headings, embedded media, internal links and author information. Build the destination layouts around your content, then test the important actions that plugins handled on the old site.
Look at your Wix website as a collection of pages and business journeys. A service site may depend on bookings and enquiries, while a publication relies on its blog archive and topic navigation. Identify those priorities before choosing the order of the move.
Prepare your move
Gather a page list, original media and the details of the Wix account that controls your content. Record any apps, forms, member areas or external booking tools used by customers.
Review your new website
Walk through the new navigation and compare the key page content with the source. Test enquiry delivery and booking links separately, then review image crops and text spacing on a phone.
A Squarespace move often combines content planning with a design refresh. Identify the pages, galleries, articles and product information that give the current site its character. Keep a visual reference for the sections you want people to recognize after the move.
Prepare your move
Share your website URL and group the content into pages, posts, projects and any store or scheduling journeys. Gather original images and note integrations managed in separate accounts.
Review your new website
Check gallery order, image captions, portfolio context and contact routes. Decide how the old navigation translates to the new structure, and review each important landing page before connecting the domain.
Begin a Shopify migration by defining what the destination should do: operate a store, present a catalog or support a separate checkout. That choice determines how product content, operational settings and customer-facing account journeys fit into the project.
Prepare your move
Inventory products, options, collections, editorial pages and campaigns. Record the services responsible for payments, fulfillment, subscriptions, customer accounts and email so each has a clear plan.
Review your new website
Treat product content and store operations as separate workstreams. Review variants and images alongside shipping, tax and payment requirements. Test the intended purchase journey before changing the website people use to place orders.
A Webflow site may combine static pages, structured collections and interactions. Map those pieces separately so the content model stays clear even when the design changes. Keep a record of the relationships that make collection-driven pages useful.
Prepare your move
List CMS collections, fields, reference relationships and the pages that display them. Note custom embeds, forms and interactions, and prepare the source access required by your selected migration workflow.
Review your new website
Review representative collection entries, including those with rich text, references or unusual media. Connect the destination content to its page layouts and test the links between related entries.
For a Framer website, review the content alongside the visual experiences built around it. Landing pages, responsive layouts and interactions can all influence how visitors understand the site. Decide what should remain familiar and what can be simplified.
Prepare your move
Gather your page structure, CMS content, original media and a visual reference for key sections. Include campaign pages, forms and embedded tools in the migration brief.
Review your new website
Check the design across common screen sizes and make sure every call to action has the intended destination. Review content hierarchy and navigation before spending time reproducing decorative interactions.
Start with the information customers rely on: services, locations, business hours, contact details and booking routes. Then identify whether GoDaddy also manages your domain, DNS or other business services so the website move does not become an accidental account change.
Prepare your move
Collect page copy, photographs and important customer links. Identify the owner of the domain and email records, and list any appointments, store or marketing tools connected to the website.
Review your new website
Check contact information across the new site, submit a test enquiry and verify the business location details. Connect the website domain deliberately while keeping email and other active services in place.
Separate the website content from the hosting and domain services around it. Collect the pages and assets you want to retain, then decide whether the move should reproduce the current structure or introduce a clearer one for visitors.
Prepare your move
Record page URLs, original images, forms and business integrations. Identify where your domain and email are managed, especially when several services are included in the same account.
Review your new website
Compare page content and navigation with the source inventory. Test forms and mobile layouts, then follow the destination domain connection instructions without removing records used by other services.
A Weebly website can hold years of business pages, blog posts and image galleries. Start by finding the content that is still useful and the pages customers still reach through old links. Use the move to make that material easier to maintain.
Prepare your move
Gather your page and post inventory, original files and any product or service information. Note connected store or payment services separately from the content pages that describe them.
Review your new website
Sample older posts and galleries as well as the current homepage. Check internal links, navigation labels and enquiries, and make sure pages used in campaigns have a destination on the new site.
Plan a Ghost migration around the publication: its articles, authors, topics and the reading experience that connects them. Treat the public content archive and the systems managing memberships or billing as separate parts of the project.
Prepare your move
Prepare your content export and source website details. Decide which articles, pages, tags and author information belong in the new publication, and retain a copy of the original material.
Review your new website
Check long-form formatting, embedded media, publication dates and links between articles. Review subscription and member journeys separately, then confirm how readers will discover the archive after launch.
Bring the history of your blog into the migration plan, including older posts that still answer reader questions. Look at labels, dates, comments and embedded media as well as the article body so the archive remains understandable in its new home.
Prepare your move
Gather the content backup and original blog URL. Sample posts from different periods of the blog, and record any external media or custom widgets that need a separate review.
Review your new website
Check article formatting, labels, image access and the relationship between old and new post paths. Recreate the navigation readers use to browse your topics and make your contact or subscription route easy to find.
Migrate Duda to Grigora
For a Duda website, document both the content model and the client-facing experience. Collections, blog content and external data connections may have different owners and update patterns. Identify which material should be copied and which connections need to be re-established.
Prepare your move
Collect the source website details and relevant partner access. Record internal collections, external data sources, blog content and the people responsible for keeping them up to date.
Review your new website
Check field relationships and representative content entries. Review widgets and external data behavior separately from a copied snapshot, and agree how the website will be maintained after handover.
A migration plan for the way you use your website.
A consultant’s website, a long-running publication and an online store should not share the same review checklist. Start with the work your site needs to do.
Small businesses and service providers
Prioritize service descriptions, locations, opening hours, enquiries and booking routes. Check that phone numbers, email addresses and calls to action remain consistent across the site. If a local campaign sends visitors to a particular landing page, include that page in the migration even when it is absent from the main menu.
Bloggers and publishers
Build the plan around your archive and publishing workflow. Decide how authors, topics and related articles should appear, and sample older posts as well as recent ones. Long-running archives often contain different media formats or layouts, so reviewing only the latest article can miss problems.
Freelancers and creative portfolios
Preserve the relationship between projects, image galleries, client context and enquiry routes. Gather the original work files you have permission to publish. A portfolio migration is a chance to make your strongest projects easier to discover and to explain your role clearly on each case study.
Agencies and client websites
Assign ownership for content, design, access and launch approval. Keep the client’s domain and business tools under the right account ownership, and document who will maintain the site after handover. Use a shared review list so feedback from several people becomes one agreed set of changes.
Creators and knowledge businesses
Map the relationship between public pages, newsletters, downloads and any gated experiences. Know which system manages the audience and which system delivers the content. Review subscription and member journeys separately from the pages that describe them, then agree how existing customers will find their next step.
Online stores and catalog websites
Separate editorial content from product records and operational store settings. Decide whether your new site is a working store, a catalog or a marketing site that links to another checkout. That decision determines the records, integrations and customer journeys you need to review.
Move your content with a structure you can maintain.
A useful content migration keeps the relationships between pages, posts and collections clear. Plan the destination structure before filling it with your archive.
Decide what to keep, improve and combine
Give each item in your content inventory a destination and an owner. Keep pages that serve a clear customer need, update material that is still useful but outdated, and identify duplicates that should become a single stronger resource. Record those choices so the person moving the content does not have to make editorial decisions along the way.
When two old pages become one, preserve the information readers still need and plan where existing links will land. Do not remove a page simply because its layout is dated; check its role in campaigns, customer support and the broader website first.
Map content fields before moving a large archive
Write down how titles, body text, summaries, dates, authors, categories and image fields should appear on the destination. For repeatable content such as team profiles, resources or listings, agree a consistent structure that your editors can use after launch. Sample a few different entries before applying that structure across everything.
Include unusual examples in the sample: an article with a table, a project with several images, a long title or an older post with an embedded video. These examples reveal formatting decisions that a short, plain-text entry would not expose.
Bring your images, downloads and embedded media.
Media deserves its own inventory. An article can look complete while a download, caption or embedded player still points at an account you plan to close.
Images and galleries
Keep the original images you want to reuse and group them by page or content collection. Review crops, focal points, captions and descriptive alt text in the new layout. Check a gallery on a phone as well as a large screen, especially when a project relies on image order to tell its story.
Documents and downloadable resources
List PDFs, brochures, menus, price lists and other files linked from your content. Confirm that each file is current, that the right person owns it and that the new page links to its intended destination. Remember resources linked from older emails or printed materials when planning the move.
Video, audio and external embeds
Identify the account that hosts each external player or embed. Check that you can still manage it after changing platforms and that its display works with the new page width. Test playback and consent behavior where relevant, and keep a readable link or description when an embed is important to understanding the page.
Keep your identity. Improve the experience.
You can migrate your website and still make deliberate design improvements. Use the existing site as a reference, then build around the needs of the people visiting the new one.
Choose the elements people already recognize
List the brand elements that should remain familiar: your name, logo, core colors, photography style and the language you use to explain your services. Keep a few screenshots of the current site as a reference for those decisions. This gives your new design continuity without requiring every old spacing choice or component to be reproduced.
Start with a small set of representative pages. Agree how a service page, an article and a contact page should look before extending the system to the entire site. This keeps the website consistent as the amount of content grows.
Review navigation, readability and mobile use together
A redesign works best when visitors can find what they need with less effort. Use clear menu names, make important actions easy to spot and keep long passages readable. Review heading order, descriptive link text and visible keyboard focus alongside the visual design.
Test practical tasks on a phone: opening the menu, reading a price or service detail, completing a form and returning to a related page. These checks tell you more about the new experience than comparing the desktop homepage alone.
Moving an online store? Plan beyond the product page.
A store migration involves content, data and day-to-day operations. Prepare separate review lists for what visitors see and what your business needs to process an order.
Catalog and product information
Inventory product names, descriptions, images, categories, options and variants. Record the identifiers your team uses to match a product across systems. Decide which items should be live at launch and which should stay archived. Review sample records with different options before committing to a catalog structure.
Checkout and store operations
Treat payments, taxes, shipping, stock handling and customer notifications as a separate configuration project. Importing product-shaped content is not the same as connecting an operational store. Agree the required checkout journey and test it using the appropriate test environment before taking live orders.
Existing customers and continuity
Plan how customers will access order information, subscriptions, account features and support after the move. Keep the records your business is responsible for retaining and decide which system remains the source of truth. Communicate any customer-facing change before closing access to an old service.
Website migration SEO: make the transition understandable.
Search visibility needs a deliberate review. Preserve the purpose of valuable pages while making it clear which URLs and content belong to the new website.
Review the pages people already find
Use your existing reports and content inventory to identify important landing pages. Keep their subject matter, useful information and next steps in view when planning the new site. Record changes so you can investigate an unexpected drop in visits or enquiries after launch.
Choose consistent canonical URLs
When several URLs show the same page, choose the version you want to represent it. Keep canonical references consistent with the URLs used in navigation and your sitemap. Review the destination’s canonical tags rather than carrying over references to an old staging address or domain.
Check indexability before launch
Review the live pages you want people to discover. Confirm that temporary development restrictions have been removed where appropriate, then inspect the rendered page titles, descriptions and headings. Treat staging controls and production indexing choices as separate decisions.
Use the sitemap as a clear inventory
Include the final pages you want discovered in the destination sitemap. Check that its URLs resolve to the intended pages and that it reflects the website you actually launched. A sitemap helps discovery; it is not a promise that every page will be indexed or ranked.
Your website platform, domain registrar and email provider may be three different services. Identify each one before changing the records that connect them.
Know who controls your domain
Confirm the registrar account, renewal contact and DNS provider for your domain. Check that the business can access those accounts and that the people involved in launch have the right permissions. Save a copy of the existing DNS records and record which ones connect the website, email and other services.
Connecting your domain to a different website platform does not necessarily require moving its registration. Decide whether a registrar transfer is part of the project or a separate task, so it does not become an unexpected dependency on launch day.
Protect email and other domain services
Follow the domain connection instructions for the destination website and change the relevant website records. Preserve the records used by your email provider and other active services. If you are unsure which record serves which purpose, resolve that question with the account owner before editing it.
After the change, test the website under the intended domain and check business email separately. Keep the old site available while you verify the new setup, and schedule the change when someone can investigate unexpected behavior.
Reconnect the tools that make your website useful.
Look beyond the homepage. Your migration review should follow information from a visitor’s action through to the person or system that receives it.
Enquiries, bookings and lead delivery
Submit each form with realistic test data and confirm where the result arrives. Review required fields, success messages, notifications and any connection to a CRM or booking system. A visible submit button is only the beginning of the journey; someone in the business must be able to receive and act on the enquiry.
Newsletters and audience connections
Identify the system that stores subscriber information and the forms that add people to it. Check list selection, consent language and any promised follow-up. Keep existing subscription preferences and account responsibilities in view when planning a change of newsletter tools.
Measurement and campaign destinations
Record the analytics, advertising and verification tools that matter to the business. Reconnect them deliberately and check that campaign links land on the intended page. Separate a missing tracking event from a genuine change in visitor behavior before drawing conclusions about the new site.
Widgets, maps and specialist tools
List maps, calendars, chat widgets, calculators and other embedded services. Confirm account access and review how each behaves inside the new layout. Test the tools that customers depend on, including their mobile display and any handoff to an external service.
Give every important old link a destination.
A URL map connects the old website to the new one. Record whether each page keeps its path, changes address, merges with another page or is intentionally retired.
A simple URL mapping example
Illustrative paths
Examples of mapping old website paths to the new website
Old path
New destination
Plan
/about
/about
Keep the familiar path.
/our-services/design
/services/design
Redirect to the matching service.
/blog/old-guide
/blog/complete-guide
Redirect to the updated resource.
/summer-campaign
Relevant current offer
Review the visitor’s original intent.
Match the destination to the original purpose
Send changed URLs directly to a relevant final page, rather than sending everything to the homepage. Update links inside the new website as well, so visitors reach the destination without unnecessary detours.
Test the paths people still use
Check important links from campaigns, partner pages and bookmarks. Verify that the new page answers the same need, then record any intentional content changes for the people reviewing the launch.
Save source exports and a list of important pages before you make changes.
Map your URLs
Keep valuable paths where possible. Add redirects for URLs that change.
Check content and SEO
Review titles, descriptions, headings, images, alt text and links.
Test the whole experience
Check desktop and mobile layouts, forms, navigation and integrations in preview.
Connect your domain when ready
Follow DNS instructions and preserve the records used for your email.
Watch the launch
Verify your sitemap, check search indexing and look for broken links.
What affects website migration time and cost?
The scope of the work matters more than a page count alone. Prepare a useful brief so you can discuss the project with realistic expectations.
Content volume and variety
A hundred similar articles can require a different amount of review from ten pages with custom layouts, forms and several embedded tools. Describe the kinds of content you have, the formats you can provide and the amount of cleanup you want to do during the move. Include old archives and downloadable files in that brief.
Design and functional changes
Keeping a familiar structure and creating a new website experience are different scopes. List the design changes, new pages and integrations you want to introduce. Agree what is essential for launch and what can become a later improvement, especially when several people need to approve the result.
Access, dependencies and approvals
Source account access, domain ownership, third-party permissions and internal review can all affect the schedule. Assign owners early and identify decisions that depend on someone outside the build team. Ask for a scope-specific estimate rather than assuming every website can move within the same fixed window.
After the move: keep improving your new website.
Launch changes where your website lives. The following reviews help you make sure it continues doing its job for visitors and for the people managing it.
Phase 1
Check the live visitor journeys
Open your important landing pages under the live domain and try the actions customers take most often. Check enquiries, bookings, downloads and any checkout handoff. Ask the people receiving those actions whether the information arrives correctly, and keep one shared list for issues found after launch.
Phase 2
Compare against the right baseline
Review visits, enquiries and page behavior against the records you saved before migration. Account for campaign changes, seasonal demand and measurement setup when interpreting the results. Investigate specific pages and journeys so a small technical problem does not disappear inside a sitewide average.
Phase 3
Check discovery and old links
Review search indexing and the destinations of important old links. Follow up on missing pages, unwanted redirects or incorrect domain references. Keep the person responsible for the domain and the person responsible for content involved until the new website is operating as intended.
Phase 4
Hand over a maintainable website
Document where pages, collections, media and connected tools are managed. Give editors a simple publishing checklist and agree who handles future domain or integration changes. A migration is more valuable when the team can comfortably update the site after the launch project ends.
Common website migration mistakes to avoid.
Most migration problems are easier to spot before launch than after a customer reports them. Give these common gaps a place in your review.
Reviewing only the new homepage
Check the pages people actually enter through: service pages, older articles, campaign landing pages and downloads. Use a varied sample during the build, then complete the inventory before launch. A polished homepage does not confirm that every content type has been handled correctly.
Closing the source account too early
Keep access to source content, exports and business records while you verify the destination. Confirm what needs to be retained before cancelling any service. A file or customer-facing feature can be easy to overlook when the old site is no longer available as a reference.
Assuming every connected tool moved with the page
A form, booking link or embedded widget can appear in a layout without the destination connection being correct. Test the complete action and verify the result in the receiving system. Record ownership so the right person can fix an integration if it stops working later.
Leaving content ownership undecided
Assign someone to check facts, someone to approve the design and someone to authorize the launch. Agree who handles future edits. Without those decisions, a migration can stall on small unresolved questions or launch with information nobody has taken responsibility for reviewing.
Everything you need for your next step.
Explore the destination before you move. These resources help you connect migration planning with the website you want to build and maintain.
Choose how to build
Explore the website-building experience before deciding how your content and page structure should fit together. Use your content inventory to identify the layouts and editing tasks that matter most.
Explore AI website creation and editing as you plan the next version of your site. Bring your own business details and review the design with the content you intend to publish.
Look for a layout suited to your content, whether that means a portfolio, publication, service website or store. Evaluate a template with real page copy and representative images.
Check destination website features, usage limits and domain requirements as part of your scope. Include both the build and the ongoing needs of the team maintaining the site.
Explore the differences between Grigora and other platforms. Compare the work you need to do after the migration, such as editing pages, publishing content and maintaining business tools.
Use the help center for product guidance while preparing the destination website. For a source-specific migration plan, contact the team with your website URL and the content you want to bring.
From keeping your domain to moving a long-running blog, get practical answers for your next step. Contact Grigora if your setup needs a closer look.
How do I migrate my website to Grigora?
Start the migration questionnaire, choose your current platform and answer a few questions about your website. Review your details, then send your request to the Grigora team. For existing content import workflows, you can also continue to the importer after sending your request.
Which website platforms can I migrate from?
Start your move from WordPress, Wix, Squarespace, Shopify, Webflow, Framer, GoDaddy, Hostinger and many more. Choose your platform to begin an import or share your website with our team for a migration plan. For a custom-built website or a platform you cannot find, choose Other platform.
Can I migrate a WordPress or Wix website?
Yes, supported content can be imported. WordPress classic imports use the migration plugin and WPGraphQL; AI websites use the WordPress REST API. Wix requires an API key and account access. Neither flow copies a complete theme, layout or app setup. Select your platform above for requirements.
Can I keep my existing domain?
You can connect a domain you own to your Grigora website on a plan that supports custom domains. Content import does not change your DNS or transfer your domain registration. Check the new website first, then follow the domain connection instructions and preserve any existing email DNS records.
Will my website design remain the same?
Content import does not reproduce your existing design. Choose a Grigora template or build a new layout, then connect or place your imported content. Recreate navigation, forms, interactive elements and integrations, and check the result on desktop and mobile.
Can I migrate blog posts and images?
The available posts and content fields depend on the source and destination website type. Accessible images can be copied by supported import flows, but private, expired or blocked media may need to be uploaded again. Review the import report, embedded media and image alt text before publishing.
Will migration affect my SEO rankings?
Rankings can change when URLs, content, layout or rendering change. Save a list of your important URLs, keep paths where possible, configure redirects for changed paths, and review titles, descriptions, headings and internal links. After launch, check your sitemap and search indexing. No importer guarantees identical rankings.
Do I need technical knowledge?
You can explore the options without an account. To import, you need a Grigora account and administrator access to the destination website. API-based sources need the right permissions, and WordPress classic imports need a plugin. If you are unsure about access or rebuilding, contact the team before starting.
Can I review my website before publishing?
Review imported content in your Grigora dashboard and use the website preview to check your layouts, links and mobile pages. An import is separate from switching your live domain. Keep the original site available until you have checked the new site and are ready to update DNS.
What happens to forms, integrations and commerce data?
Recreate and test forms, third-party integrations, custom scripts and navigation separately. Importing product-shaped CMS records does not configure a working store, checkout or inventory integration. Customer accounts, passwords, subscriptions and billing data are outside the content import scope.
Can I migrate a custom-built website or a platform not listed here?
Yes, you can start by choosing Other platform. Share your current website URL, the content you want to bring over and any important features. Our team will help you assess the move and plan your new website on Grigora.
How much does migration cost?
Review current Grigora pricing and the limits of your destination website before proceeding. Source platforms may also restrict API access or exports. For a guided migration, share your website with our team to discuss the scope and any service costs before you proceed.
Can I migrate a website and keep the same URL?
You can plan a platform change around the same domain and page paths. Record the existing addresses and compare them with the destination structure. If any paths change, map each important old address to its most relevant new page and test those links before launch.
What is the difference between website migration and a domain transfer?
Website migration moves content, design and functionality to a different website setup. A domain transfer changes the registrar responsible for the domain registration. Connecting an existing domain to a new website can be a separate DNS change. Decide which of those tasks your project actually needs.
Can I move only my blog and leave the rest of my website?
You can scope a migration around part of a website. Decide where the blog will live, how navigation will connect the two sites and which system owns each URL. Review the domain and linking setup with the team before moving a section independently.
Should I redesign my website during the migration?
A migration can be a useful time to improve navigation, page layouts and the editing workflow. Record the content you need to retain and the design changes you want as separate decisions. Approve a few representative pages before extending the new design across the whole site.
What should I back up before switching website platforms?
Keep a copy of the source content, original media and downloadable files. Save the current page inventory and DNS records, and retain any business records your organization needs. Make sure the backup can be opened and understood before relying on it as the only copy.
Can I migrate more than one website?
Plan each website separately, even when several share a brand or owner. Identify the destination website, domain, content structure and approver for each move. Review your Grigora plan and account permissions before preparing several destinations. A phased launch can make the review work easier to manage.
What information should I send with a migration request?
Include the current website URL, source platform, approximate content volume and the features that matter most. Explain whether you want to keep the design or refresh it, and mention who controls the domain. Do not put passwords, API keys or private customer exports into the contact message.
How do I estimate the size of a website migration?
Count content types as well as pages. Include posts, collections, galleries, downloads, forms, integrations and operational store requirements. Describe unusual layouts and the approvals needed for launch. Those details create a more useful scope than a page total on its own.
What happens to old images and PDF links?
Include them in your inventory rather than checking only the page text. Decide where the destination files will live and update the pages that link to them. Test important downloads and externally shared file links, especially before closing an account that hosts the originals.
Can I keep my business email when moving my website?
Plan the website DNS change separately from email. Identify your mail provider and preserve the records it requires. After connecting the new website, test sending and receiving email as well as loading the website. If a bundled service is changing, review that dependency with the account owner.
Should I cancel my old website subscription before migrating?
Keep the source available while you gather exports and verify the destination. Check what content, records and linked services you need to retain before cancelling. The right cancellation point depends on your plan, account terms and the checks still outstanding after launch.
How can an agency manage client approval for a migration?
Use one shared inventory and an agreed acceptance checklist. Assign people to review content, design and business tools, then name the final launch approver. Record decisions in one place so contradictory feedback does not turn into separate, competing versions of the website.
What should I check first after the new website goes live?
Try the journeys that matter most to the business: finding a service, sending an enquiry, booking, downloading a resource or reaching checkout. Verify the result in the receiving system. Then review the remaining page inventory and follow up on broken links or missing content.
Can I use a new template when migrating?
Yes, your content plan and design choice can be handled together. Choose a layout that fits the kind of information you publish, then review representative pages with real content. Test long titles, large galleries and detailed articles so the design works beyond an idealized sample.
Can I migrate a website built with an AI website builder?
Choose your current tool in the platform selector, or choose Other platform for a custom-built site. Share the live URL and describe the content, code, data connections and features you want to keep. Plan the destination around those needs and review the important workflows before launch.
Your next website starts with what you’ve already built.
Choose your platform. Understand the options. Take the next step.
