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.
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.
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 eight to nine 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 - 6 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.
- Post-launch support. Fixes and minor updates - 1 week.
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 Results
MinIO moved platforms without a redesign, and kept the team that moved it.
The site went onto Webflow with its design intact.
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.
FAQ
Beqi migrated MinIO's website to Webflow - about 70-100 pages and five CMS collections - with technical SEO, accessibility, integrations, and training, then stayed on as MinIO's Webflow team.
The migration was scoped as a fixed plan of eight to nine weeks, including a full week of QA and client review.
Acceptance criteria were written into the agreement before work started: every page loading in Chrome, Firefox, Safari, and Edge, no critical SEO or accessibility issues, working CMS collections, and working integrations.
Yes. The ongoing partnership began in August 2025 and has been renewed twice.
