Moved to Webflow, then renewed twice

How Beqi migrated MinIO's site to Webflow in a fixed-scope plan with QA built in, then stayed on as its Webflow team.

88 unique pages

Migrated to Webflow, design preserved

6 weeks

Scoped plan, including a full week of QA

2x

Partnership renewals since August 2025

FROM THE CLIENT

"Beqi's been a true technical partner for our web team—fast, flexible, and always willing to jump in where we need them. They've helped bring both structure and scalability to how the website is built behind the scenes, which has made it so much easier for our marketing team to move as fast as MinIO is growing."
Kelsey Kenyon

Kelsey Kenyon

Head of Integrated Marketing

Key takeaways

MinIO needed its site on Webflow with the same design, the same responsive behaviour, and its search footprint intact.

Beqi ran a fixed-scope migration with written acceptance criteria and QA as its own phase.

After launch MinIO kept Beqi on as its Webflow team and has renewed the partnership twice.

01

The Challenge

MinIO needed its marketing site on Webflow without changing how it looked or worked: the same design, the same responsive behaviour, the same brand.

It also needed a marketing team that could manage content on its own afterwards, and a search footprint that survived the move.

02

The Solution

The migration

  • Pages. About 70-100 pages rebuilt in Webflow, matching the existing layout, styling, and responsive behaviour.
  • CMS. Five CMS collections with their fields, templates, and dynamic pages.
  • Technical SEO. Titles, meta descriptions, and heading hierarchy on every page, an XML sitemap, 301 redirects, and canonical tags.
  • Accessibility. An audit and fixes across all pages and images: ARIA labels, alt text, keyboard navigation.
  • Integrations. Third-party scripts connected, and MinIO's ROI calculator integrated together with MinIO's engineering team.
  • Training. A how-to video library showing MinIO's team how to add and edit CMS content and static pages.

Timeline

The migration was scoped as a fixed plan of six weeks, with QA as its own phase rather than an afterthought.

  • Discovery and planning. Requirements review and sitemap - 2 days.
  • Development. Page templates, CMS setup, integrations - 4 weeks.
  • SEO and accessibility audit. Technical SEO and accessibility fixes - 3 days.
  • QA and client review. Testing and revisions - 1 week.
  • Launch. Go-live on Webflow and DNS cutover - 1 day.

QA: what "done" meant

Acceptance criteria were written into the agreement before work started, so both sides knew what would be tested.

  • Browsers. Every page loads without errors in Chrome, Firefox, Safari, and Edge.
  • Audits. SEO and accessibility audits report no critical issues.
  • CMS. Collections work correctly, and MinIO's team can add and edit content.
  • Integrations. Every third-party integration operates as specified.
  • Staging. Changes are reviewed on a staging domain before they reach the live site.

After launch: the partnership

When the migration finished, MinIO kept Beqi on as its Webflow team. Requests go into a direct Slack channel and are worked one at a time, in the order MinIO sets, with no cap on how many can be queued.

  • Pages. New pages, layout changes, components, and interactions for campaigns and events.
  • CMS at scale. Bulk work across the blog and resource library - for example, fixing social share images on more than 250 blog posts in one pass, then standardising them across blog posts, customer stories, and resources.
  • SEO hygiene. Titles, headings, slugs, and redirects kept in order as the site grows.

‍

The MinIO blog running on Webflow CMS
The MinIO blog on Webflow - one of the CMS collections Beqi works on in bulk.
03

The Results

MinIO moved platforms without a redesign, and kept the team that moved it.

The site went onto Webflow with its design intact.

A MinIO product page on Webflow
A product page on min.io, running on Webflow.

MinIO's marketers manage CMS content themselves, with a how-to video library to refer to.

The partnership began in August 2025 and was renewed in February 2026 and again in August 2026.

Visit the live site: min.io

About these results

Migration scope: Beqi’s project proposal dated April 21, 2025, subsequently accepted by MinIO. The proposal specifies approximately 88 pages and about five CMS collections. These are scope estimates, not a verified final delivery count.

FAQs

What did Beqi do for MinIO?
How long was the migration planned to take?
How was QA handled on the MinIO migration?
Does MinIO still work with Beqi?
Next case study

Axiom Space

Trusted by 140+ enterprise and fast-growing teams

Move to Webflow. Keep what already works.

Planning a migration like MinIO’s? We’ll scope your pages, CMS, integrations and SEO requirements, then build a migration plan with QA and handover included.