Skip to main content

Search

Welcome to Support

Migrating from the Legacy Editor to Content Editor 2.0: Process, Template Chooser & Known Legacy Bugs

  • Updated

Overview

TeamSideline is moving all organizations from the legacy content editor to Content Editor 2.0 (also called the New Content Builder / New Site Builder). Editor 2.0 offers modern templates, drag-and-drop editing, a larger widget library, improved formatting controls, and mobile optimization. This article explains how to start your migration, what happens during it, and how known limitations of the legacy editor are handled during the transition.

If you are contacting support because a formatting or image problem cannot be fixed in the legacy editor, migrating to Editor 2.0 is usually the recommended resolution.

How to Start Your Migration (Template Chooser)

Migrations are handled as a guided process. Our Content Team will reach out when it is your organization's turn, but you can also request to start now:

  1. Go to the Template Chooser: https://templatechooser1.teamsidelinesite.com/
  2. Enter your organization's information and select the template you want. This also moves your migration date up if you want to start sooner.
  3. The TeamSideline Content Team will be in touch to guide you through the rest of the process.
  4. The team sets up the core structure of your new site (for example at yourorg.teamsidelinesite.com) as a preview for you to review before it goes live.
  5. Review the preview site and make any needed edits. Your site is made live on the scheduled Go Live date. If you need more time, reply to your migration email to adjust the date.

What Gets Migrated Automatically vs. Recreated Manually

Your back-end data is not affected by the migration. Based on how support has described the process, the following applies:

Transferred automatically:

  • Programs (Registrations)
  • Schedules
  • Calendar
  • Locations
  • Downloads
  • Core elements such as your logo and Contact Us page

Recreated manually in Editor 2.0:

  • Front-end text content and images
  • Custom pages
  • Content tables
  • Other custom content from the content area

Your Admin Site Map stays the same — there are no major backend layout changes. The main difference is that front-end website content is now edited directly in the in-line editor.

Custom URLs are not changed — if you use a custom domain, your web address remains the same after migration.

Known Legacy Editor Bugs (Resolved by Migrating)

Several recurring problems exist only in the legacy editor and are resolved by moving to Editor 2.0:

  • Board / gallery images display incorrectly. Images may show in a single large column on the live site even though they appear correctly (smaller, in rows) while editing. This is a known legacy-editor issue that the new content tool resolves.
  • News Item formatting glitches. Issues such as white/near-invisible bullet text on the public page, or backspace "whiting out" an entire line, are known legacy issues that are not scoped for a legacy fix because of the migration.
  • Large images that cannot be deleted. Inserting a very large image can lock the page so the image cannot be removed in the editor. Upload smaller images; if a page is already stuck, support can remove the image on the back end.

HTML Editing Limitations in the Legacy Editor

The legacy editor exposes tools for fonts, colors, borders, and cell alignment (including in content tables), but there are important limitations to be aware of:

  • Direct HTML edits can overwrite formatting. When support corrects a page by editing the underlying HTML directly (for example, to fix missing table borders), original attributes such as font colors, bolding, and text alignment may be lost and must be reapplied manually.
  • Missing editing toolbar / no gear icon. If you click a page and no attribute toolbar or gear icon appears, click Switch to Editor while viewing the page to load the editing toolbar.
  • Complex tables (schedules/standings) are hard to maintain. As an alternative to hand-formatting a table, you can create the content as a PDF and upload it via Content > Page Edit for more consistent formatting, or use TeamSideline's built-in Schedules/Standings tools.

After Migration

Once your site is live on Editor 2.0, note that some menu paths change. For example, Google Analytics is set under More > Settings > Google Tools rather than Administration > Configurations. See the New Content Builder articles for editor-specific tasks, and "Fixing Common Post-Migration Site Issues" for locked elements, registration button URLs, and leftover HTML.