Migrate to Bricks / Oxygen

Oxygen to Bricks migration - modern dev workflow, same control

Keep the granular control you loved in Oxygen. Get the modern ecosystem and active development of Bricks.

Review my Oxygen siteSee the migration process
Feature parityOxygen → Bricks
  • Oxygen classesGlobal classes
  • Custom selectorsCustom CSS
  • Code blocksCode element
  • Reusable partsComponents
  • JSON templatesBricks templates
  • Repeater / dynamic dataQuery loop
// what we preserve
1:1Oxygen classes → Bricks globals
Codecustom CSS and PHP carried over
SEOmetadata and redirects mapped
Fixedquote and timeline up front

The problem

Oxygen still works - but the ground is shifting

Nothing on your site is broken today. The case for moving is about trajectory, not failure - here's the honest read.

The Oxygen 4.0 / Breakdance split One team, two builders. The fork left the long-term roadmap ambiguous.± roadmap
Slower release cadence Fixes and features now land further apart than the ecosystem moves.− cadence
A smaller third-party ecosystem Fewer add-ons, frameworks, and learning resources to draw on.− ecosystem
  • Momentum has moved Bricksforge, Frames, and an active community are where new tooling lands.− momentum

    • Agency-safe workflow

    Agency-safe migration protocol

    Your agency stays front-and-center. We rebuild Oxygen architecture in Bricks behind your brand, preserve the intent of class systems and dynamic data, and document decisions before launch.

    White-label by default

    No BricksGenius branding in the client workflow. Communication runs through your agency unless you approve otherwise.

    Agency owns the relationship

    Your team stays front-and-center for client updates, approvals, and final presentation. We support the technical rebuild behind the scenes.

    Staging-first rebuild

    Migration work happens away from the live client site first, with review points before launch-sensitive changes move forward.

    Technical calls stay controlled

    If a client technical call is useful, it happens only with your approval and with your agency present.

    Launch handoff included

    You receive QA notes, migration decisions, redirect guidance, and builder-specific risk notes for internal review or client-safe delivery.

    Deliverables

    What you get

    A full rebuild in Bricks that treats your Oxygen architecture as something to preserve - not something to redo from scratch.

    • Oxygen class system mapped 1:1 to Bricks global classes
    • Custom code, code blocks & snippets preserved
    • ACF and Meta Box field integrations honored
    • JSON-based Oxygen templates ported to Bricks templates
    • Hooks and filters preserved where the architecture allows
    • Custom selectors and stylesheets migrated intact
    • Dynamic data, query loops & conditional logic rebuilt
    • Reusable parts converted to Bricks components
    • Responsive breakpoints reconstructed to match
    • 301 redirect map for any changed URLs
    • Before / after Core Web Vitals report
    • Clean Oxygen removal after launch sign-off

    Process proof

    What your handoff includes

    Oxygen migrations need architecture evidence, not generic assurances. Your handoff shows how classes, templates, custom code, and dynamic data were treated in Bricks.

    Class system mapping

    Oxygen classes, utility patterns, reusable structures, and naming decisions are mapped so Bricks does not become a one-off visual copy.

    ACF and Meta Box review

    Dynamic fields, repeaters, conditionals, archives, and data-dependent layouts are checked before template decisions are locked.

    Custom code inventory

    PHP, JavaScript, CSS, snippets, and plugin-dependent behavior are listed with what was rebuilt, retained, or flagged.

    Template architecture notes

    Singles, archives, reusable parts, query structures, and conditional logic are documented for agency review.

    Query loop and dynamic data checks

    Bricks query loops, dynamic tags, fallback states, and content-source assumptions get QA notes before launch.

    Launch risk notes

    Architecture risks, plugin dependencies, redirect needs, and SEO-critical carryover items are captured in the handoff.

    Built to be reused by your agency. This is process proof, not a result claim. It shows how the migration is controlled before any client-facing launch.

    Execution quality

    Execution quality you can show internally

    A quick look at the kind of structured Bricks work, component thinking, and visual polish your agency can expect during handoff.

    Staging review artifact

    Review

    Staging review

    The agency reviews the build before handoff. Fixes happen in the agreed review window, not through vague back-and-forth after launch.

    Staging before handoff

    No vague back-and-forth after launch.

    Structure handoff

    Structure handoff

    Global classes, templates, reusable sections, and Bricks-specific decisions are documented so your team can maintain the site later.

    Documented structure

    Handoff notes replace guesswork.

    Migration map

    Migration map

    Migration work gets URL, metadata, redirect, form, and template checks before the old builder is removed.

    URL and redirect checks

    No broad Lighthouse promises on inherited stacks.

    Performance evidence

    Performance evidence

    Performance claims stay tied to agreed URLs and eligible conditions, especially on inherited stacks.

    Measured against agreed URLs

    No broad Lighthouse promises without control over the stack.

    Reviews

    Client words, earned through execution.

    We know that outsourcing can feel like a risk. These reviews reflect our commitment to the fundamentals of a seamless partnership. Judge us by the habits that matter most to your timeline: hitting deadlines, writing maintainable code, and keeping communication clear.

    WordPress Security Hardening
    I have worked with Ranjan several times in the past. He is knowledgeable, efficient, and always very professional. He went the extra mile to ensure additional levels of security were in place to help protect our investment in the future.
    RWRyan WallaceWordPress and server client
    Custom WordPress Development
    Ranjan was fantastic to work with. His coding expertise is top-notch, he quickly understood my needs and delivered clean, efficient work. Very professional, polite, and always respectful of deadlines.
    JOJamie OuelletteOwner, High Peaks Marketing
    WordPress Speed Optimization
    My website is now lightning fast thanks to his technical optimization work. He was polite, extremely cooperative, and went above and beyond to help my business.
    NMNeil McDonaldFounder and Director, Climaxx Media Ltd
    Custom WordPress Development
    The deliverable was far faster than I expected and excellent quality work. If I need WordPress services again, I would not hesitate to ask Ranjan first. He clearly knows what he is doing with WordPress.
    RBRobert BurbridgeBoard Member, Agape Corner
    Web Design & Development
    Very professional and skilled web designer. The website was delivered exactly as requested, with great attention to detail. Communication was smooth, and everything was completed on time.
    FDFrancesco Della MalvaCEO and Co-Founder, Multimedia Vibes
    Web Design & Development
    I have worked with a lot of designers and Ranjan is top-tier. Will order again.
    ESEfrain SanchezFounder and CEO, Growth Logiq
    Technical Migration
    Highly recommend for challenging hosting and WordPress requirements. He handled a complex technical migration quickly and flawlessly, with zero issues.
    SBSam BohrCEO and Founder, National Courses
    Simple & Efficient Process
    The process was simple and efficient. I'm really pleased with the outcome.
    PSPeter Robert StoneAttorney and Counselor at Law, Peter Robert Stone APC
    Perfect Service
    Perfect service from start to finish. Thank you, Ranjan.
    VPVincent PolletCreator, Choucroute Party / Atomic Games
    Collaborative Project Delivery
    He did an excellent job, and I'm pleased with the results. He brought great suggestions throughout the project, many of which we incorporated. I'd likely work with him again.
    KGKevin GatesInland House Buyers
    Fast, Reliable Delivery
    Amazing, fast, and absolutely worth recommending.
    USURSA-SECURSA-SEC LLC
    WordPress Technical Support
    The professionalism, code expertise, and attention to detail were top-notch. Excellent communication, quick responses, and great cooperation. Highly skilled in WordPress setup.
    HRHrusaWordPress and VPS setup client
    WooCommerce Performance
    This might be my fifth order with Ranjan. I highly recommend his services. He helped resolve a complex WooCommerce performance issue and got the backend working smoothly.
    EREdouard RuolLuminaire Celeste
    Web Design & Development
    Ranjan exceeded expectations with his code expertise and professionalism in web development. His deep understanding and proactive communication made working with him a breeze.
    SSSeoSoftSEO reports / tools platform
    Professional Code Quality
    Ranjan's professionalism and code expertise made this project a success. His proactive communication and politeness made the collaboration even better. Highly recommended.
    CMCoiffure MobileCoiffure Mobile
    Consistent On-Time Delivery
    He consistently delivered high-quality work on time across every project I assigned him. I highly recommend him.
    WSWithSponsorCreator sponsorship platform
    Responsive Collaboration
    Ranjan was responsive and understanding throughout the work. I'd happily work with him again.
    RMRory MacParlandCurion
    Repeat Client Feedback
    Excellent work as normal.
    ARAshley RickardIntercom Repair / Intercom Master
    Smooth Team Collaboration
    Working with Ranjan and team was great. Wonderful work.
    DADealership AcceleratorAI lead management for dealerships

    Pricing

    Three tiers matched to your build

    Pick by site complexity, not page count alone. Every quote is fixed before work starts.

    Starter

    Contained Oxygen sites with a tight class system and little custom code.

    Starting at $1,100 fixed quote after review

    • Up to 10 pages migrated
    • Oxygen classes mapped to Bricks globals
    • Core templates ported
    • Content & SEO metadata preserved
    • 301 redirect map
    • Before / after performance report
    Request a fixed quote
    Most popular

    Standard

    Real Oxygen builds - CPTs, ACF, and a structured class architecture.

    From $2,200 fixed quote after review

    • Everything in Starter
    • Up to ~30 pages migrated
    • Custom post types & taxonomies ported
    • ACF / Meta Box integrations rewired
    • Custom code & snippets preserved
    • Dynamic templates & query loops rebuilt
    Request a fixed quote

    Premium

    Code-heavy, integration-driven Oxygen sites at any scale.

    From $4,500+ quote only

    • Everything in Standard
    • Unlimited page deliverables
    • API integrations & custom REST endpoints
    • Advanced ACF flexible content
    • WooCommerce / multilingual support
    • Priority turnaround & extended support
    Request a fixed quote

    Starting prices shown; most Standard-tier migrations fall between $2,200 and $4,500. Payment: 50% to begin, 50% on launch sign-off. Includes two revision rounds against the agreed design. Final fixed quote is confirmed after reviewing the number of unique pages and templates, custom-code volume, dynamic-data complexity, forms, WooCommerce, integrations, animation complexity, SEO/redirect work, and launch-risk notes - page count alone isn't the whole picture. Third-party licences and hosting are billed separately. Not included: content rewriting, brand redesign, or SEO strategy beyond technical migration.

    How we work

    Six steps, with the class system up front

    1. 01
      Day 1–2 - Audit

      Oxygen audit

      Templates, class system, custom code, ACF, and plugins fully inventoried.

    2. 02
      Day 2–3 - Class map

      Class system extraction

      Oxygen classes and selectors extracted and mapped to Bricks global classes.

    3. 03
      Day 3–7 - Rebuild

      Bricks rebuild on staging

      Site rebuilt against the mapped class system - design preserved.

    4. 04
      Day 6–8 - Code port

      Code & integration port

      Custom code, hooks, filters, and ACF / Meta Box wiring carried across.

    5. 05
      Day 8–9 - SEO

      SEO & redirect check

      Metadata verified, redirect map applied, parity checked against the old site.

    6. 06
      Day 9–10 - Launch

      Launch & Oxygen removal

      Go live with rollback ready; Oxygen removed cleanly after sign-off.

    Why us

    We migrate Oxygen's architecture, not just its pages

    The technical case

    • We read Oxygen's class architecture. Classes, selectors, and stylesheets are extracted and mapped - structure survives the move.
    • Preserve, don't rebuild from zero. Custom code, hooks, and filters carry across. We don't discard working logic to "start clean".
    • JSON templates ported structurally. Oxygen's JSON templates are read as data, not rebuilt by eye - conditions and assignments included.
    • Devs talk to devs. You're technical - so is the migration call. No oversimplified hand-holding.

    What the mapping looks like

    class-map.txt
    # Oxygen class system  ->  Bricks globals
.oxy-header        →  .header
.oxy-header__nav   →  .header__nav
.oxy-card          →  .card
[ct_code_block]    →  Code element
oxygen.json tmpl   →  Bricks template
# selectors + stylesheets preserved

    Naming and structure stay yours. You won't relearn your own stylesheet on the other side of the migration.

    Comparison

    Stay on Oxygen vs. migrate to Bricks

    An honest side-by-side - including where the two are simply even.

      Stay on Oxygen Migrate to Bricks
    Development velocity Slower release cadence post-split Frequent, active releases
    Community & tooling momentum Smaller, quieter ecosystem Bricksforge, Frames, ACSS, active forums
    Roadmap clarity Focus split across Oxygen 4.0 & Breakdance Single product, clear direction
    Third-party add-ons Limited selection Broad, growing marketplace
    Hiring & documentation Fewer devs, thinner docs Larger talent pool, extensive docs
    Class-based granular control Full control Full control - preserved in migration

    FAQ

    Oxygen migration questions

    Oxygen and Bricks are architecturally close - both class-based and code-friendly. The reason to move isn't features, it's trajectory: a faster release cadence, a larger third-party ecosystem, and a clear roadmap after the Oxygen / Breakdance split. Because the mental model carries over, migration is a low-risk move.

    The class system is the core of the migration. We extract your Oxygen classes and selectors and map them 1:1 to Bricks global classes, so structure and naming survive the move - you won't relearn your own stylesheet.

    Yes. Code blocks, custom PHP, and snippets are carried across. We preserve working logic and don't rewrite it unless you ask. Hooks and filters are kept where the architecture allows - a few Oxygen-specific hooks have direct Bricks equivalents, and we flag any that don't during the audit.

    Oxygen's JSON-based templates are read structurally, not screenshotted. Each becomes a Bricks template with the same conditions and template assignments, so dynamic pages keep behaving the way they do today.

    Yes. ACF and Meta Box field groups, dynamic data, and query loops are honored and rewired to Bricks' dynamic data system. Field keys and group logic stay intact - nothing is re-keyed.

    Waiting is a position, not a plan. If your roadmap depends on the platform's, the split is exactly the uncertainty worth migrating away from. Bricks' direction is unambiguous today, and migrating now means you're not racing a forced timeline later.

    Yes - that's the Premium tier. Custom post types, taxonomies, advanced ACF flexible content, REST endpoints, and API integrations are all in deliverables. CPT-driven architecture ports cleanly because Bricks' query loop maps directly onto Oxygen's repeater logic.

    Send your current site and a short note on scale and custom code through the form below. We'll reply after review with a fixed quote, handoff deliverables, and launch-risk notes.

    No direct client communication by default. Your agency stays front-and-center. If a technical call is useful, it happens only with your approval and with your agency present.

    Yes. The migration can run behind your agency brand with staging review, agency-safe handoff notes, and no BricksGenius branding in the client workflow.

    We check SEO-critical content, metadata, heading structure, internal links, redirect requirements, and launch QA items. For larger migrations, a redirect map and staged review happen before launch.

    A staged Bricks build, QA notes, migration decisions, builder-specific risk notes, and launch guidance your agency can use internally or adapt for the client.

    Request a fixed quote

    Start your Oxygen to Bricks migration

    Send the essentials - site URL, rough page count, and how much custom code is involved. We'll reply with a fixed quote and timeline, usually within one business day.

    • Fixed quote, no hourly surprises
    • Direct line to the developer doing the migration
    • Staging-first workflow with a rollback plan

    Reply within one business day. No mailing list, no follow-up sequence.