Recognizing the pressing need for time-saving solutions and streamlined processes, we are delighted to unveil the remarkable feature of school cloning. By cloning your school:
a. You ensure consistency across schools
b. Save time for recreating a school structure from scratch.
This functionality empowers Organization Owners and Super admins (with the respective permissions) to effortlessly duplicate their schools.
Cloning is available only for schools on the Learning Center plans or higher. The created cloned school can only be upgraded to the Learning Center plan or higher.Let's dive into the step-by-step process of cloning a school.
Clone your LearnWorlds school
1. Access your LearnWorlds school via LearnWorlds as an Organization owner or Super admin (if you have the relevant permissions).
2. Navigate to Schools.
3. Hover over the specific school you desire to clone and click on Clone school.
4. As you click on the Clone school button, a sideform will appear. This sideform serves the following purposes:
- Add the new school domain.
- Select the Courses to clone. You can clone all courses from the school or select specific ones. You can also specify if courses will stay in sync (this option is available with an additional add-on). You can find out more about course syncing in this article.
- Select the school data that you wish to clone.
- Take note of the mandatory data that is auto-selected by default.
5. When you are ready to proceed, click on Clone school.
- It is not possible to clone a school that utilizes the legacy Pages Builder.
- The ability to clone schools is exclusively available for those subscribed to the Learning Center or higher plans.
- A cloned school can only be upgraded to the Learning Center plan or higher.
You are allowed to have a maximum of one non-purchased cloned school. To clone another school, you must either purchase a pricing plan or delete the existing cloned school.
Upon cloning a school, a new status called Cloned is assigned, which essentially functions as disabled. Until you purchase a pricing plan, you can only access the cloned school's Account & Billing page.
Cloned schools will have the same payment/billing details as the original school since they belong to the same organization.
What Gets Cloned?
The cloned school replicates a wide range of configurations, including settings, course content, design layouts, and automations. Below is a breakdown of what can be cloned.
a. School Settings
| Setting | Notes |
| General School Settings | Name, logo, language, time zone |
| Site Flavors | Active flavor/theme |
| Login & Registration Settings | Includes options & 2FA (Social login settings are not cloned) |
| Privacy & Cookie Settings | GDPR settings, cookie banner |
| Email Notifications | Templates, signatures, and toggle states |
b. Courses & Bundles
| Element | Notes |
| Course Settings & Descriptions | Name, visibility (free/private/draft) |
| Course Structure | Units and sequencing |
| Layout Pages | Per-course layout, including tag-based visibility |
| Pricing & Access Rules | Price, enrollment conditions, drip schedule |
| Course Automations | Trigger-based actions per course |
| Course Rules | Prerequisites, progress locks, access limitations |
| Enrollments & User Progress | Users and their progress are not cloned |
| Bundles | Groupings of courses |
| Visuals | Thumbnails, featured images |
| Course Content Activities | Includes text, SCORM, video, assessments, eBooks, embeds, files, and tagging |
c. Pages & Layouts
| Element | Notes |
| Page Layouts | Landing pages, custom designs |
| System Pages | Login, registration, dashboards, player |
| Block Visibility Settings | Tag- or role-based content display |
| Custom Blocks & CSS | HTML and CSS styling |
| Sections & Templates | Reusable layout elements |
| Marketing Forms & Surveys | Forms and surveys are cloned, but user responses are not cloned/importable |
d. Automations & Tags
| Element | Notes |
| Active Automations | Triggers, actions, and targets |
| Tags per Segment | Used for user and content segmentation |
| Tag Naming & Visibility Logic | Includes tag-based visibility flows |
| Tag Flows | Progression logic based on tag assignment |
e. Users & Roles
| Element | Notes |
| Custom Roles | Roles are cloned, but users themselves are not |
| Users | You’ll need to manually export/import users if needed |
| Community Spaces | Community activity and posts are not cloned or importable |