When to Consider FlexLab
Breadcrumb
-
- Codeless
- When To Consider FlexLab
Applies to: Codeless
Overview
Codeless and FlexLab both host Drupal, but they target different teams. This guide helps you decide when to start (or move to) FlexLab instead of staying on dashboard-only Codeless.
Key concepts
- Codeless — editors and marketers work in Drupal admin and the FlexSite dashboard; no Git required.
- FlexLab — developers own the codebase in GitLab; deploys flow through pipelines and merge requests.
- Migration — moving an existing Codeless site to FlexLab is a planned project (content export/import), not a single button.
Signs you may need FlexLab
- You need a custom Drupal module or PHP that cannot be installed from the dashboard.
- Your agency requires merge request review before production deploys.
- Developers want local copies of the database via
flexsite db pull. - Theme Marketplace limits block your design system — your theme must live in Git with CI-built assets.
Steps — start fresh on FlexLab
- From Projects, click New Project.
- Choose Drupal 11 with the Flexlab label (not Codeless Drupal CMS).
- Pick Blank template and complete the wizard.
- Open Code, clone the repository, and onboard developers with FlexSite CLI Setup.
Moving from existing Codeless
There is no one-click Codeless → FlexLab conversion. Typical approach:
- Export content and configuration from Codeless (Backups + Drupal migration tools).
- Create a new FlexLab project and import into the Git-backed site.
- Reconnect Digital Assets and Domains on the new project.
Atom sites should Upgrade to Codeless first, then evaluate FlexLab separately.
-
Codeless
- Creating a Codeless Project
- Accessing Drupal Admin (Quick Login)
- Theme Marketplace
- Managing Environments
- Publishing to a Custom Domain
- One-Click Module Updates
- Quality and Lighthouse Reports
- Build Settings and Credits
- Backups (Database and Files)
- DAM Integration
- Site Templates (Starter, Byte, Haven)
- When to Consider FlexLab