That was the core tension in our work with BMW Classic: how do you modernize without disrupting a highly specialized, globally shipping operation? Here’s what actually happened, and what we learned.

The real problem wasn’t the old technology

BMW Classic runs one of the most specialized online shops in the motorcycle world – genuine parts for everything from 1920s classics to current models, with worldwide shipping. The platform they were running had done its job for years, but it had reached its limits:

• SEO was essentially broken. The site was barely indexed, which meant customers searching for long-tail spare parts – often very specific queries – simply couldn’t find the shop. 
• Content updates were slow and risky. 
• The system wasn’t built to support modern marketing workflows or a smooth purchasing experience.

The hidden complexity: a significant portion of the business logic lived inside FileMaker, a legacy database system that had accumulated years of operational knowledge – product structures, compatibility rules, fulfilment logic. That’s not something you just switch off.

Keeping the business running while rebuilding it

The biggest architectural decision we made early on was this: don’t replace FileMaker in a big bang. Build around it, carefully.

This meant designing a dedicated sync layer – a structured integration that connects FileMaker with the new custom-built storefront, keeps product and catalog data in sync, and insulates the shop from the risks that come with legacy data sources. If FileMaker becomes temporarily unavailable, the shop keeps running. That stability is only possible because of the abstraction layer between them.

What this taught us is that preparation and understanding of the existing system matters more than the technology you’re migrating to. We spent significant time with the architects of the old shop before writing a single line of the new one. That investment paid off directly in the quality of the integration.

Two systems, two responsibilities: why Payload CMS was the right call

A shop like BMW Classic needs two fundamentally different things working in parallel: a structured commerce layer for parts data, pricing, compatibility, and stock – and a flexible content layer for landing pages, campaigns, and editorial storytelling.

Trying to force both into a single system creates compromises in both directions. So we separated them intentionally.

Payload CMS became the content brain. It gave the BMW Classic team the ability to publish and update marketing content, build campaign pages, and manage editorial material without needing a developer for every change. That kind of operational independence matters – especially for a team managing a catalog this size.

The custom commerce layer handled the rest: product data, checkout, pricing, and order flow. Connected through the sync layer, both systems together gave BMW Classic something they didn’t have before – speed without risk.

SEO as a product requirement, not an afterthought

One of the clearest decisions we made going in was to treat SEO as a core requirement – not a layer added after development. For a shop selling 40,000+ spare parts, organic discoverability isn’t a nice-to-have. It’s the difference between capturing long-tail search demand and missing it entirely.

In practice, this meant:

• A clean, indexable URL and navigation structure from day one
• Fast page loads via Next.js and Digital Ocean infrastructure
• Scalable metadata and content architecture that grows with the catalog
• A navigation model built around the way real customers actually search – by model family, then category, then part

The previous platform had essentially no SEO foundation. Fixing that structurally, rather than patching it, was one of the most commercially relevant things we did in this project.

What we’d do the same – and what we’d watch more closely

The design and technical architecture held up well. Building a storefront around the real buyer journey – find the right model, navigate categories confidently, validate part details, purchase without friction – is the right approach for a parts shop at this scale.

What we’d watch more closely next time: even more rigorous documentation of FileMaker data structures before migration begins. Legacy systems often contain edge cases that only surface under real conditions. The more thoroughly you map the old system upfront, the fewer surprises appear during sync testing.

The other key learning – and this applies beyond BMW Classic – is that a sync layer isn’t just a technical workaround. It’s actually a long-term architectural feature. Future migrations, additions, or replacements of any single component don’t require rebuilding the whole platform. That’s a real advantage as the business evolves.

Where things stand

The shop is live, stable, and continuing to develop. We’re ongoing with SEO improvements, UX refinements, and expanding the content layer. A project like this doesn’t end at launch – it enters a growth phase, and the foundation needs to be solid enough to support that.

If there’s one thing worth taking away from this project: the hardest part of migrating a legacy system isn’t the new technology. It’s respecting and understanding the old one well enough to build around it safely.

Working with a content-heavy platform or considering a CMS migration? Our Payload CMS services are built for exactly these kinds of projects – complex data, editorial independence, and no big-bang risk.

Related: Learn how we developed an ERP-Shopify connector and merged the e-commerce store for Rokker.

The post E-Commerce and CMS Migration for BMW Classic appeared first on what. AG.

That’s a surprisingly powerful idea. And it’s more practical than it sounds.

The real problem most SMEs face

Most small and mid-sized businesses don’t suffer from a lack of software. They suffer from too much of it – and none of it talking to each other.

Customer data lives in one tool. Project statuses in another. Product information is buried in spreadsheets. Internal requests arrive by email or Slack. And the website? Completely disconnected from everything else.

The result is predictable: duplicated data, manual handovers, inconsistent processes, rising software costs, and internal tools that never quite fit the way the business actually works.

This is exactly the environment where a flexible, central system creates real value.

Why Payload CMS is different from a typical CMS

Payload started as a headless CMS, but it’s increasingly used as a broader application framework. Its collections model lets you define structured data for literally anything — and each collection automatically gets a full admin interface plus REST and GraphQL APIs.

That means instead of building a backend, admin UI, permissions model, and API layer from scratch, teams can start with Payload and shape it around their actual business processes.

In practice, you can model things like leads, customers, contacts, offers, orders, projects, service tickets, suppliers, internal approvals, documents, and employee requests. All in one system, all with APIs ready to go.

That’s a very different proposition from “the blog engine.”

What this looks like for a growing SME

Imagine a Swiss SME in technical services or distribution. They have a sales pipeline, recurring customer projects, service requests, product data, quotes managed in an accounting tool, marketing content on their website – and a pile of Excel sheets holding it all together.

They probably don’t need a massive ERP rollout. Too expensive, too rigid, too slow.

What they need is a central system where they can track leads and customer accounts, manage project statuses, store product and service data, assign tasks internally, connect data to the website, and sync selected records with accounting or reporting tools.

Payload can serve as exactly that core. One shared backend for both business operations and digital presence. CRM-like data – companies, contacts, opportunities, sales stages – sits alongside operational records like orders, project statuses, service cases, and approval flows. And the same system powers the website: service pages, product pages, case studies, blog posts, FAQs, downloadable files.

Neat little beast.

Why this architecture works so well

Structured business data and content live in the same place

A quote is content. A project status is content. A customer note is content. Once you stop thinking of a CMS as just a publishing tool, a different picture emerges – and Payload’s collection model makes it easy to model any business entity cleanly.

Internal tools get built much faster

The expensive part of internal software isn’t the database – it’s everything around it: admin screens, forms, validation, access rights, search and filtering, audit-friendly workflows, APIs for integrations. 

Payload gives a lot of that foundation out of the box. For an SME, that means starting with a focused use case – say, lead management plus project tracking – and expanding step by step rather than funding a giant transformation project upfront.

Headless means one source of truth, multiple outputs

Because Payload is headless, the same core data can power a website, a customer portal, an internal dashboard, a mobile app, or a third-party reporting tool. Much healthier than copying data between tools and hoping nobody forgot to update row 847 in a file called FINAL_v3_REAL.xlsx.

Integrations are straightforward

Payload supports REST, GraphQL, and Local API access, which makes it well-suited to integration-heavy environments. 

It can connect cleanly with accounting platforms, existing ERP software, email and marketing tools, e-commerce systems, BI dashboards, document generation services, and automation platforms. 

The idea isn’t necessarily to rip out every existing system – often the smarter move is to use Payload as the flexible middle layer that orchestrates the processes that matter most. More on that in our article on integrating your CMS with ERPs and CRMs.

CRM + ERP lite: often better than a bad big system

There’s a category of company that’s too operationally complex for spreadsheets, but not big enough to justify a heavy ERP implementation. That company often ends up in an awkward swamp – the CRM is too sales-focused, the ERP is too rigid, the website CMS is disconnected, and employees work around the tools instead of with them.

A Payload-based setup can be a pragmatic middle path.

Not because it magically replaces every enterprise tool. But because it lets you build the exact workflows you need, with the exact data structures your company already uses.

A simple example:

1. A sales manager creates a lead.
2. It becomes an opportunity.
3. When won, it generates a project record.
4. The project links to deliverables, contacts, and documents.
5. Selected data syncs to accounting.
6. The customer portal shows project status.
7. Marketing reuses the same product data on the website.

That’s not science fiction. That’s just good architecture.

Where this approach makes sense – and where it doesn’t

This model works especially well for:

• B2B service providers 
• distributors
• agencies
• technical service firms
• niche e-commerce companies 
• manufacturers with custom workflows
• companies building partner or customer portals. 

Basically: any SME with unique internal workflows that’s frustrated by rigid SaaS tools and wants to reduce duplicate data entry.

It’s less suited to companies that need a highly specialised enterprise ERP with deep finance, procurement, warehousing, compliance, and multi-country complexity. Payload is not the answer to every process problem.

But for SMEs that need speed, flexibility, integration, and control – it’s a very strong foundation. Especially when the alternative is a patchwork of tools that sort of work individually and collectively behave like a committee of confused pigeons.

Reading tips: If you’re also weighing whether a CMS upgrade or full relaunch makes more sense for your situation first, our guide on system upgrade vs. full relaunch can help you think it through. And if you’re coming from a legacy platform, it’s worth understanding the hidden costs of staying put before making any decisions.

The strategic advantage of a central system

The biggest advantage here isn’t technical – it’s organisational.

When your central system reflects the way your business actually works, you get better visibility, fewer manual steps, cleaner handovers, faster process changes, and better use of your existing data. And because Payload sits at the centre of both content and operations, it helps break the old separation between “the website” and “the business.”

In reality, they were never separate worlds. The website, sales pipeline, service process, product data, and internal workflows are all part of the same company story. A central system should reflect that.

Ready to explore what this could look like for your business?

At what., we specialise in Payload CMS services – from building modern websites to setting up Payload as a central operational backbone for growing companies. We also help businesses with tools integration, connecting your CMS with the systems you already rely on – ERPs, CRMs, marketing platforms, and more.

If you’re curious whether Payload could work as more than just a CMS for your business, we’re happy to take a look together. Sometimes a short conversation is all it takes to see what’s possible.

The post Payload CMS: A Central Hub for Company Processes appeared first on what. AG.

Here’s why it became our go-to platform for new projects.

Modern tech stack we already love

Payload CMS is built with Node.js, TypeScript, React, and Express – technologies our team already uses daily. This familiarity makes the development process significantly smoother and faster.

We work with tools we understand deeply, which means fewer compatibility issues and a codebase that stays clean and maintainable. No outdated plugins, no legacy workarounds, no fighting with ancient libraries.

Payload feels fresh and modern, which makes our work more efficient and honestly more enjoyable.

Headless freedom for any type of build

Traditional CMS platforms tightly couple backend and frontend, limiting creativity and flexibility. Payload CMS is fully headless, meaning content lives in the backend and can be delivered to any frontend via APIs – React, Next.js, Vue, mobile apps, digital displays, anything.

This architecture allows us to build lightning-fast websites, custom applications, multi-platform experiences, and redesigns without touching the content structure. It gives clients more possibilities and fewer restrictions.

When a client wants to refresh their design two years later, we don’t need to rebuild the entire CMS – just the frontend.

Developers genuinely enjoy using it

When developers enjoy their tools, the work quality improves dramatically. Payload CMS offers a code-first approach with typed content models, auto-generated REST and GraphQL APIs, hooks, granular access control, and deep customization options.

The admin UI is beautiful and responsive, and the development experience is consistent and logical throughout. Instead of wrestling with plugins or debugging messy systems, we build great features and solve real business challenges.

This developer happiness translates directly into better outcomes for clients – faster delivery, cleaner code, and more innovative solutions.

Editors love the user-friendly admin panel

A CMS should empower content editors, not confuse them. Payload CMS provides a clean, modern admin panel where clients can easily update pages, upload media, manage content, and publish blog posts without training or frustration.

When clients feel confident using their CMS, everything runs smoother. They gain independence, and we receive fewer “How do I update this?” support requests.

The interface is intuitive enough that most editors can figure it out themselves, yet powerful enough to handle complex content structures.

Perfect for custom or complex projects

Some CMS platforms work well for simple sites but struggle when requirements get sophisticated. Payload CMS actually shines with complexity – whether you need intricate data structures, multi-step workflows, advanced integrations, custom applications, or comprehensive multi-language support.

Whether we’re building a corporate website, product catalog, customer portal, or content-heavy platform, Payload gives us the flexibility and scalability we need. It never feels like we’re fighting the system to achieve client requirements.

For specialized needs like migrating from Django CMS to a modern platform, Payload’s flexibility makes the transition significantly smoother than traditional alternatives.

No more plugin headaches

Working with older platforms often means dealing with outdated plugins, broken dependencies, version mismatches, or conflicts after updates. Payload’s architecture avoids this completely.

Most functionality is built through clean, maintainable code instead of relying on inconsistent third-party plugins. This results in fewer surprises, fewer bugs, and a much healthier system overall.

We’re no longer at the mercy of plugin developers who abandon their projects or introduce breaking changes without warning. The stability this provides is invaluable, especially when clients depend on their website for business-critical operations.

Truly future-proof technology

Web technology evolves rapidly, and a CMS should help you keep pace – not hold you back. Payload CMS is actively maintained, built with modern languages, integrates seamlessly with contemporary frontend frameworks, and is designed to scale.

Clients don’t want a CMS they’ll need to replace in a few years. Payload gives them something durable and genuinely future-ready.

Unlike the hidden costs of staying on legacy CMS platforms, investing in Payload means investing in sustainable technology that won’t become a maintenance burden.

Payload CMS helps us deliver better results, faster

At the end of the day, our CMS choice is about giving clients the best possible outcome: fast performance, excellent UX, strong SEO foundations, clean code, smooth integrations, and a system they genuinely enjoy using.

Payload CMS helps us deliver all of that faster and with fewer complications. When the technology gets out of the way, we can focus on creativity, strategy, design, and solving real business needs.

Our clients notice the difference – in launch timelines, ongoing maintenance costs, and the ease of managing their content day-to-day.

Final thoughts

Choosing Payload CMS wasn’t a random decision – it was a natural evolution for our agency. We needed a CMS that’s modern, flexible, loved by developers, and easy for clients. Payload delivered exactly that.

These days, it’s the platform we prefer for new projects, and our clients appreciate the results just as much as we do.

At what.digital, we specialize in Payload CMS services – helping businesses build fast, scalable, and maintainable websites. Whether you’re migrating from an older platform or starting fresh, we have the experience to bring your vision to life.

Reading Tip: Find out why Payload CMS is the best choice for modern websites.

The post Why Our Agency Chose Payload CMS for New Web Projects appeared first on what. AG.

The good news? Migrating from Django CMS to a modern, headless CMS like Payload CMS is more straightforward than you might think. Payload offers a developer-first approach built on Node.js, React, and TypeScript – technologies that are fast, flexible, and built for the future.

In this post, we’ll walk you through why migrating from Django CMS to Payload CMS makes sense and provide a step-by-step guide to help you make the switch smoothly.

Why Migrate from Django CMS to Payload CMS?

Moving from a traditional CMS like Django CMS to a modern headless CMS brings several benefits – especially in performance, flexibility, and long-term maintainability.

Headless Architecture for Greater Flexibility

One of the biggest advantages of Payload CMS is its headless architecture, which separates your content backend from your frontend presentation layer. Unlike Django CMS, where frontend and backend are tightly coupled, Payload gives you complete freedom to deliver content via APIs to any frontend – whether that’s a website, mobile app, or IoT device.

This means you can customize your user experience without being locked into a specific templating system. You can also create multi-channel experiences more easily, serving the same content across different platforms.

Better Performance and Scalability

Over time, Django CMS can become sluggish and difficult to scale, especially as outdated plugins and integrations pile up. Payload CMS is built with modern, performance-optimized technologies that deliver content quickly and efficiently.

Its headless structure pairs beautifully with frontend frameworks like Next.js or React, letting you build highly performant, SEO-friendly applications. As your business grows, Payload scales with you – without requiring constant architectural rewrites.

Developer-Friendly and Customizable

Payload CMS takes a developer-first approach, making it easier for technical teams to build, maintain, and customize. Built with Node.js, TypeScript, and React, it uses tools that developers already know and love.

Payload’s code-first content modeling lets you define custom fields, relationships, and content types that match your exact needs. This level of flexibility is often missing in traditional CMSs like Django CMS, where you’re forced to work within pre-defined structures and templates.

Security and Maintenance

As Django CMS ages, keeping it secure and up-to-date becomes increasingly difficult. Payload CMS is actively maintained, with regular updates and security patches.

Its API-first design also makes it easier to integrate with modern security protocols, ensuring your content stays protected. You won’t be stuck dealing with outdated plugins or security holes that never get patched.

For more on the risks of staying on legacy platforms, check out our article on the hidden costs of legacy CMS platforms.

Steps for Migrating from Django CMS to Payload CMS

A successful migration requires careful planning, clean data preparation, and a clear understanding of your new system’s capabilities. Here’s how to approach it step by step:

1. Plan Your Migration Strategy

Before you start moving data, outline your plan. Key questions to answer:

• Content Structure: Review your current content types, page templates, and media assets in Django CMS. How will these map to Payload’s content models?
• Frontend Framework: Payload is headless, so you’ll need to choose a modern frontend framework like Next.js, React, or Vue.js. Pick the one that best fits your team’s skills and project needs.
• Migration Timeline: Will you migrate everything at once, or phase by phase? Phased migrations let you move gradually and reduce risk, while an all-at-once approach can be faster but riskier.

2. Set Up Payload CMS and Configure Content Models

With Payload CMS, you define content models in code rather than through the admin interface, giving you much more flexibility and control.

Start by setting up collections (Payload’s version of content types) and defining the fields you need – text fields, image uploads, relationships between content types, and more. You can also use custom hooks to add business logic to how content is processed.

Payload provides a powerful admin panel where your content editors can easily manage their work. The interface is customizable, so you can adapt it to match your team’s workflow.

3. Migrate Your Content

Once your content models are ready, it’s time to move your data from Django CMS to Payload CMS.

For smaller websites, you can manually copy and paste content. For larger sites, you’ll want to automate the process using scripts or custom tools. You’ll need to map the old Django CMS content structure to the new models in Payload.

Make sure your media files (images, documents, etc.) are properly migrated and stored in Payload’s media library – or set up a third-party service like Amazon S3 for better asset management.

4. Rebuild Your Frontend

Since Payload CMS is headless, your frontend will need to be rebuilt—and this is where you gain the most flexibility.

If you’re using React or Next.js, you can easily fetch content from Payload CMS using its built-in REST or GraphQL API. Your content will be dynamically rendered on the frontend, giving you full control over the user experience.

This is also your opportunity to modernize your design and improve performance.

5. Test and Optimize

Once the migration is complete, thoroughly test your new site to catch any issues before going live.

Check for broken links, missing content, or discrepancies between the old and new systems. Optimize the frontend for SEO by ensuring content is properly structured and implement schema markup where necessary.

6. Launch and Monitor

After testing, you’re ready to launch your new Payload CMS-powered site.

Monitor the site closely after launch for any performance issues or bugs and address them quickly. Since Payload CMS is headless, you’ll be able to scale your system easily in the future – adding new content types or expanding integrations as your business grows.

Bottom Line

Migrating from Django CMS to Payload CMS offers businesses a modern, scalable solution that’s easier to maintain, more secure, and better equipped for the future.

By following the migration steps outlined above, you can reduce complexity, improve performance, and ensure your website stays adaptable as technology evolves.

If you’re looking to modernize your CMS and future-proof your digital content, Payload CMS is the ideal choice.

Need help with your migration? At what.digital, we specialize in CMS migration services – especially to modern, flexible platforms like Payload CMS. Our team has extensive experience in planning and executing smooth, successful migrations.

Reading Tip:Learn more about why Payload CMS is the best choice for modern websites in 2025.

The post Migrating from Django CMS to Payload CMS: A Modern Approach appeared first on what. AG.

In 2026, Payload CMS has become one of the most popular choices for building fast, scalable, and future-proof websites. Let’s explore why.

What Is Payload CMS?

Payload CMS is a headless and open-source content management system (CMS).

Being “headless” means that the content (the backend) is separate from the design and layout (the frontend). This allows developers to use any frontend technology – like React, Vue, or Next.js – to display content.

Payload CMS is built for developers, but also provides a simple and powerful admin panel for editors. It combines flexibility, speed, and full control over content management.

Why Choose Payload CMS in 2026

1. Built with Modern Technology

Payload CMS is built using Node.js, TypeScript, and React, the same technologies that power many of today’s most advanced web applications.

This means faster performance, easier integration with modern frameworks, and long-term sustainability.

2. Headless and API-First

Because it’s headless, Payload CMS delivers content through REST and GraphQL APIs. This makes it easy to connect to any type of frontend – websites, apps or webshops.

It’s also future-proof: when you redesign your site or app, your backend doesn’t need to change.

3. Developer-Friendly and Fully Customizable

Developers love Payload because it’s code-first. You can create and manage content types using simple code, not complicated admin settings.

This makes it easier to maintain, version control, and customize – perfect for teams working in modern development environments.

4. Beautiful and Easy Admin Dashboard

Payload includes a ready-to-use admin interface where editors can easily create, edit, and manage content.

You can even customize the dashboard to match your team’s workflow or brand style – something that’s much harder with older CMSs.

5. Secure and Self-Hosted

Unlike some cloud CMS platforms that store your content on their servers, Payload allows you to host your data wherever you want – giving you full control and improved security.

It also uses up-to-date libraries and strong user permissions to keep your site protected.

6. Scalable and Performance-Focused

Whether you’re building a small business site or a large content platform, Payload CMS can scale easily.

It’s optimized for speed, works well with caching and CDN solutions, and integrates smoothly with frameworks like Next.js, making your site fast and SEO-friendly.

7. Open Source and Actively Supported

Payload CMS is open-source, meaning it’s free to use and backed by an active developer community. Regular updates, bug fixes, and improvements ensure the system stays reliable and cutting-edge.

How Payload CMS Compares to Other CMS Platforms

Payload CMS combines the best of both worlds: the flexibility of a headless CMS with the control and affordability of self-hosting.

When to Use Payload CMS

Payload CMS is a great choice if you:

• want full control over your data and hosting
• need a custom, fast, and modern web application
• use React, Next.js, or other JavaScript frameworks
• are replacing an old CMS with too many legacy plugins
  

It’s ideal for startups, digital agencies, and growing businesses that value flexibility and speed over pre-built templates.

The Bottom Line

In 2026, Payload CMS stands out as one of the most modern and powerful CMS platforms available. It offers the freedom of a headless system, the strength of modern web technologies, and the flexibility developers and content teams need.

If you’re planning to relaunch your website or move away from an outdated CMS, Payload CMS is a smart, future-ready choice that will save time, improve performance, and reduce technical debt.

Looking for expert guidance? An experienced agency specialized in Payload CMS implementations can help you build a fast, scalable, and maintainable website. Whether you’re migrating from an older platform or starting fresh, the right agency has the experience to bring your vision to life.

The post Payload CMS: The Future-Proof Solution for Websites in 2026 appeared first on what. AG.