Classic Bonzai vs Modern Bonzai 2
A comprehensive guide to understanding the architectural differences and planning your migration from Classic SharePoint to Modern SharePoint with Bonzai 2.
Setting Realistic Expectations
Migrating from Classic Bonzai to Bonzai 2 is not a simple upgrade. It involves:
- • Platform change: Classic SharePoint → Modern SharePoint (different page model)
- • Content recreation: Modern pages must be built fresh; classic pages cannot be converted
- • Configuration migration: Brick settings must be manually recreated in SharePoint
- • User training: Content authors need to learn the new editing experience
Plan for weeks to months of work, depending on your site complexity and number of pages.
Who This Guide Is For
Site Administrators
Migration planning, infrastructure decommissioning, and deployment coordination.
- Migration planning
- List/data migration
- Deployment steps
Content Authors
Learn the new editing workflow and understand what changes in your daily work.
- Workflow differences
- Page editing changes
- New capabilities
Developers
Technical details on architecture changes, APIs, and customization options.
- Tech stack changes
- API differences
- Icon mapping
What This Migration Actually Means
Bonzai 2 eliminates the need for Brick (AWS infrastructure) and simplifies deployment to a single .sppkg file. However, this is a platform migration, not an upgrade. You are moving from Classic SharePoint (publishing sites, master pages, JSOM) to Modern SharePoint (communication sites, SPFx, REST APIs). This requires rebuilding pages and reconfiguring web parts.
Executive Summary
This document provides a comprehensive comparison between Legacy Bonzai (running on Classic SharePoint with Brick administration) and Modern Bonzai 2 (running on Modern SharePoint with SPFx).
| Aspect | Classic Bonzai | Bonzai 2 (Modern) |
|---|---|---|
| Platform | Classic SharePoint (Publishing Sites) | Modern SharePoint (Communication Sites) |
| Technology | bonzai.min.js + JSOM/CAML | SPFx + React + REST API |
| Administration | Brick (AWS-hosted) | SharePoint native + Theme Manager |
| Deployment | CDN + Brick provisioning | App Catalog .sppkg upload |
| Theming | Brick Theme Editor | Theme Manager web part |
| Web Parts | 23 XmlWebPart-based | 29 SPFx React-based |
| Extensions | Master page / bonzai.min.js injection | Mega Menu + Footer (SPFx Application Customizers) |
What Changed & Why
Understanding why things changed helps you make better decisions during migration. Here are the key architectural changes and their benefits:
No external infrastructure required
All code runs within SharePoint, no AWS/CDN dependency
Why: Microsoft modern SharePoint doesn't support custom master pages or external script injection. SPFx runs safely in the SharePoint container.
No Brick administration
All configuration done in SharePoint property panes
Why: Eliminates separate login, reduces costs, and keeps configuration close to the content.
Instant updates
No CDN propagation wait time (previously 5-15 minutes)
Why: SPFx packages are hosted by Office 365 CDN automatically, with immediate cache invalidation.
Native SharePoint integration
Uses SPFx framework, Fluent UI, and REST APIs
Why: Aligns with Microsoft's roadmap, ensuring long-term compatibility and support.
Responsive by default
Mobile-first design built into all web parts
Why: No separate mobile templates needed - one design works everywhere.
Workflow Comparisons
These comparisons illustrate how common tasks differ between Classic and Modern SharePoint. Note that these are per-task comparisons—the overall migration effort involves many such tasks across your entire site.
Adding a Web Part to a Page
Comparing the editing experience (not counting initial learning curve)
Classic Bonzai
- 1
Log in to SharePoint (Classic)
Navigate to site
- 2
Click "Edit Page"
- 3
Identify the correct web part zone
- 4
Go to Insert → Web Part
- 5
Find "Bonzai" category in list
- 6
Select web part and click "Add"
- 7
Click dropdown → Edit Web Part
- 8
Type list name manually
Exact spelling required!
- 9
Type view name manually
- 10
Click "OK"
- 11
Check in page
- 12
Publish page
Pain Points
- Manual list/view name entry prone to typos
- Fixed zones limit placement options
- Check-in/check-out workflow adds steps
Bonzai 2
- 1
Navigate to page
- 2
Click "Edit" button
- 3
Click "+" where you want the web part
- 4
Type "Bonzai" → Select web part
- 5
Click pencil → Select list from dropdown → Publish
Benefits
- Dropdown pickers reduce errors
- Flexible placement on the page
- Real-time preview as you configure
Changing Theme Colors
After Theme Manager is already set up
Classic Bonzai
- 1
Open new browser tab
- 2
Navigate to Brick URL
- 3
Log in with AWS Cognito credentials
- 4
Search for your site collection
- 5
Click theme icon to open Theme Editor
- 6
Find color property in editor
- 7
Change color value
- 8
Click "Save"
- 9
Click "Publish"
- 10
Wait 5-15 minutes for CDN propagation
- 11
Hard refresh SharePoint page
Pain Points
- Separate login required
- CDN propagation causes delays
- Cannot preview on actual page before publishing
Bonzai 2
- 1
Navigate to page with Theme Manager
- 2
Click Edit on page
- 3
Use Theme Manager color pickers
- 4
See changes in real-time
- 5
Click Save Theme, then Publish page
Benefits
- No separate login needed
- Changes visible immediately
- Preview on the actual page
- Dark mode toggle built-in
Feature Migration Guide
Each Classic Bonzai feature has a modern equivalent. This table shows what changed and what action you need to take:
Key Features: What Changed
Migration Checklist
Time Estimates: These are rough estimates for a single site with moderate complexity (~20-50 pages, standard web parts). Large organizations with multiple sites, custom configurations, or complex content structures should expect significantly longer timelines. Plan for pilot testing before full rollout.
Your Migration Journey
Work through these phases systematically. Do not rush—each phase builds on the previous.
Realistic Total Timeline
- Small site (10-20 pages): 2-4 weeks with dedicated resources
- Medium site (20-50 pages): 4-8 weeks with dedicated resources
- Large site (50-100+ pages): 2-4 months, often done in phases
- Enterprise (multiple sites): 6-12 months for full rollout
These estimates assume dedicated migration resources. If migration is done alongside regular work, multiply by 2-3x.
Cancelled Web Parts & Alternatives
One Classic Bonzai web part is not available in Bonzai 2. Here's why, and what to use instead:
Marketplace is back in Bonzai 2
The Marketplace web part has been re-implemented for Modern SharePoint and ships in Bonzai 2. It now points at any SharePoint list with dynamic columns, filtering, sorting, and an optional create button, and can be rendered on a page, in Teams tabs, or as a full-page app. See the mapping table below for parity details.
Delve
Why removed: Microsoft is retiring Delve as a standalone experience. Its functionality is being integrated into other Microsoft 365 experiences.
Alternatives:
- • Trending documents → SharePoint home "Recommended"
- • Find people → Microsoft Search
- • View profiles → Microsoft 365 profile cards
- • Content discovery → Viva Connections
What You Don't Need Anymore
One of the best parts of migrating to Bonzai 2 is all the complexity you can stop worrying about:
Web Part Mapping
Bonzai 2 ships with 29 web parts. 22 of them map directly to legacy Bonzai web parts (see the table below), and 7 are brand new capabilities with no classic equivalent (see New Capabilities in Bonzai 2 further down). The "Parity" column indicates approximate feature coverage—not all legacy options are available, and some new options have been added:
| # | Legacy Web Part | Modern Equivalent | Status | Parity |
|---|---|---|---|---|
| 1 | Advanced Links | Bonzai Advanced Links | Implemented | 95% |
| 2 | Important Messages | Bonzai Important Messages | Implemented | 95% |
| 3 | Feedback | Bonzai Feedback | Implemented | 90% |
| 4 | Document Rollup | Bonzai Documents Rollup | Implemented | 95% |
| 5 | Favourite Documents | Bonzai Favourite Documents | Implemented | 95% |
| 6 | Favourite Sites | Bonzai Favourite Sites | Implemented | 95% |
| 7 | News Rollup | Bonzai News Rollup | Implemented | 90% |
| 8 | Events Rollup | Bonzai Events Rollup | Implemented | 90% |
| 9 | Spotlight Rollup | Bonzai Spotlight Rollup | Implemented | 95% |
| 10 | Landing | Bonzai Landing | Implemented | 90% |
| 11 | Slider | Bonzai Slider | Implemented | 90% |
| 12 | Pages Rollup | Bonzai Pages Rollup | Implemented | 95% |
| 13 | Documents Table | Bonzai Documents Table | Implemented | 95% |
| 14 | Document Portal | Bonzai Document Portal | Implemented | 85% |
| 15 | Employee Directory | Bonzai Employee Directory | Implemented | 90% |
| 16 | People Listing | Bonzai People Listing | Implemented | 90% |
| 17 | Locations | Bonzai Locations | Implemented | 90% |
| 18 | Site Directory | Bonzai Site Directory | Implemented | 90% |
| 19 | Site Directory Favourites | Bonzai Site Directory Favourites | Implemented | 95% |
| 20 | Search Box + Refinement | Bonzai Advanced Search | Implemented | 85% |
| 21 | Tabbed | Bonzai Tabbed | Implemented | 90% |
| 22 | Marketplace | Bonzai Marketplace | Implemented | 85% |
New Capabilities in Bonzai 2
The following 7 web parts are new in Bonzai 2 and have no Classic Bonzai equivalent. They unlock modern patterns (on-page theming, News/Event/Spotlight hero pages, card grids, image galleries) that were not practical on Classic SharePoint's publishing model.
Theme Manager
On-page theme customization with real-time preview, light/dark modes, and footer branding controls. Replaces the Brick Theme Editor.
Page Banner
Full-width hero banner for News, Event, and Spotlight pages. Auto-detects page metadata and exposes engagement actions (share, like, comment, add-to-calendar).
News Sidebar
Companion sidebar for News pages that renders Related Links, Contacts, and Tags.
Event Sidebar
Companion sidebar for Event pages with Related Links, Contacts, and Tags.
Spotlight Sidebar
Companion sidebar for Spotlight pages featuring the Spotlight profile plus Related Links, Contacts, and Tags.
Content Cards
Responsive grid of cards sourced from any SharePoint list, with icons, titles, descriptions, and call-to-action links.
Image Link Gallery
Clickable image gallery tile grid driven by a SharePoint list, with optional manual image mode, pagination, and favorites.
22 legacy mappings + 7 new = 29 web parts
This matches the 29 web parts listed in the Web Parts Reference, which is the authoritative inventory. If you just upgraded, make sure to refresh your App Catalog package so the new web parts appear in the Bonzai 2.0 toolbox.
Extensions
Bonzai 2 also ships two SPFx Application Customizers — tenant-level extensions that run site-wide from the Bonzai2.sppkg package. These replace functionality that was delivered via Classic master pages and bonzai.min.jsscript injection, both of which are blocked in Modern SharePoint.
Extensions: What Changed
Mega Menu
3-level hierarchical navigation with desktop mega menu panels and a mobile drawer, driven by a MegaMenuNavigation list. Hides the native SharePoint navigation and mobile app bar by default, and also hosts the Bonzai license banner on page load.
Footer
List-driven site footer with navigation columns, optional feedback form, and Theme Manager–managed branding. Automatically suppressed on Site Contents and list/library admin surfaces so it does not disrupt SharePoint system pages.
Footer docsTwo-step activation for extensions
Uploading Bonzai2.sppkg to the App Catalog is not enough. For each site where you want Mega Menu or Footer to appear, you must also add the Bonzai app via Site Contents → New → App → Bonzai 2, or register the customizers in the Tenant Wide Extensions list if "Apps you can add" is blocked by policy.