A Starter Folder Structure for a Department Team

Questions

  • How should we organize our department's files in Microsoft Teams?
  • Should each folder from our old Microwave (J:) drive become its own channel?
  • How many channels should a department Team start with?
  • How deep should folders go inside a Teams channel?
  • Where do old files we rarely open belong?
  • What should stay in my OneDrive instead of going into the department Team?
  • How should we name folders and files in a Teams channel?
  • What does a good structure look like for an academic department?
  • Where do faculty searches, evaluations, and other supervisor-only files go?
  • Can we change the channel structure after the migration is finished?

Environment

Creating, renaming, and rearranging channels in a Microsoft Team requires Team owner permissions. The Bowdoin College Service Desk runs department migrations off the Microwave (J:) drive, and a department gets a better result by bringing a draft structure to that conversation rather than a copy of the old drive.

  • Applies to department heads and Team owners planning a migration, and to anyone reorganizing a Microsoft Team that already exists.
  • Microsoft Teams in a web browser, in the desktop app on Windows 11 or on macOS Sequoia (15.x), Tahoe (26.x), or newer, and in the Teams app on the current version of iPadOS.
  • Bowdoin-issued computers and tablets are supported. Personal devices are best effort only.
  • Every Team should have at least two owners before a migration starts.
  • Not in scope: creating the Team itself. For those steps, see Create a Microsoft Team in the Related Articles section.
  • Not in scope: deciding which material should not travel to Teams at all. For that, see What Not to Move into Teams in the Related Articles section.

Resolution

Important: Decide the channel structure before any files move into the Team. Rearranging channels afterward is possible, but it breaks the links and shortcuts that people have already created.

Channels replace the top-level folders of the old drive

Channels replace the top-level folders of the Microwave (J:) drive, and folders inside a channel replace the subfolders. Every standard channel is a folder in the Team's connected SharePoint library, which is why the old drive and the new Team line up so neatly.

What does not carry over is the count. A channel is for a group of people or a body of work, not for every folder that existed on the department drive. A channel appears in the sidebar for everyone in the Team and carries its own conversation, so twenty channels means twenty places to check. Twelve top-level folders on an old drive usually become four or five channels.

Example structure for a mid-size administrative office

  • General: Announcements, Meeting Notes, Templates
  • Operations: Procedures, Forms, Vendor Records
  • Budget: Budget FY26, Invoices, Reports
  • Projects: one folder per active project
  • Communications: Web Content, Print, Photos
  • Department Archive: one folder per year

Add one private channel, typically named Personnel, for searches, evaluations, and anything only supervisors should see. Do not use a private channel for ordinary work that most of the department needs.

Note: Files in a private channel are stored on a separate SharePoint site that only members of that channel can reach, so the restriction is enforced by the system rather than left to etiquette.

Example structure for an academic department

  • General: Meeting Notes, Department Handbook, Templates
  • Curriculum: Syllabi, Course Proposals, Assessment
  • Events: Speakers, Logistics, Posters
  • Department Archive: one folder per academic year

Faculty searches belong in a private channel of their own, named for the search rather than for the year.

Give rarely opened material a Department Archive channel

Every department has material it must keep but rarely opens: closed projects, superseded policies, past years' reports. Give that material one channel named Department Archive and one folder per year inside it. A Department Archive channel keeps the working folders short without pushing anything out of reach, and it makes the annual cleanup obvious.

Material that needs institutional preservation is a separate question. The College Archives runs a Records Management Program that advises on records of enduring value, and those records should be discussed with the College Archives rather than filed in a channel and forgotten. For what to leave behind and how to close out finished work, see What Not to Move into Teams and Archive Teams and Folders in Microsoft Teams in the Related Articles section.

Naming and nesting rules that keep the structure healthy

  • About three levels of nesting. Channel, folder, subfolder. Past three levels, people stop finding things and file paths grow long. The maximum path length is 400 characters, and deep nesting with long names reaches 400 characters faster than most people expect.
  • Short names. Names accumulate down the path. Do not repeat the department name or the channel name in a folder inside that channel.
  • Sortable dates. Write dates as YYYY-MM-DD, so that 2026-03-14 Minutes sorts correctly. Never write 3-14-26.
  • No "Misc", "Old", "Stuff", or "New folder". Folders with those names are where files go to be lost. If something does not fit a folder, it belongs in the Department Archive channel or nowhere.
  • One authoritative copy. Version history is built in, so keep one file and let Teams track the changes rather than saving final, final v2, and final USE THIS. For how to open an earlier version, see See and Restore an Earlier Version of a File in the Related Articles section.
  • Libraries and views that stay manageable. Performance falls off above roughly 100,000 files in a library, and a folder view holding more than 5,000 items hits a display threshold. If a folder is heading toward either figure, split it by year or by function. For the full set of documented figures, see Best Practices and Limitations in Teams, SharePoint, and OneDrive in the Related Articles section.

What belongs in your OneDrive instead of the department Team

Put in your OneDrive anything that is yours: drafts nobody has seen, personal notes, reference copies you downloaded, and work in progress you are not ready to share. Move a document into the Team when the document becomes the department's. Files in a channel belong to the Team rather than to a person, and those files stay in place when someone leaves the College. For how the three places differ, see Understand Files in OneDrive, Teams and SharePoint in the Related Articles section.

Start with fewer channels than feels right

Create the smallest set of channels that covers the work, put everything else in folders, and add channels when people ask for them. Adding a channel later is a small change. Splitting a channel that already holds a year of files and links is not. For changing a structure that people are already using, see Add, Move, and Remove Channels After Your Team Is Running and Rename a Team, Channel, or Site in the Related Articles section.

Do the cleanup before the move rather than after. For help deciding what actually needs to come along, see Manage and Clean Up Department Files Before the Teams Migration and Using the File Review Spreadsheet to Organize Your Department Files in the Related Articles section.

Additional Help

If you need further assistance, you have several options:

  • Bowdoin Bot: Chat with Bowdoin Bot directly from any KB page for instant answers.
  • Phone: Call the Bowdoin College Service Desk at (207) 725-3030.
  • In person: Visit the Tech Hub in Smith Union during business hours.
  • Submit a ticket: Request assistance through the Service Catalog.

Additional Resources

 

 

AI-assisted content: This article was created with AI. It was verified and edited by a human.
Print Article

Related Articles (16)

Access a Department Network (Microwave) Drive
Instructions for connecting to a Bowdoin department (J:) drive on the Microwave file server from a personal or Bowdoin computer running macOS, Windows, or Linux. Includes the VPN requirement for connecting from off campus.
Add, Move, and Remove Channels After Your Team Is Running
This article explains how a Team owner adds channels to a Microsoft Team that is already in use, moves files between channels without losing version history, and removes channels the department no longer needs. It also explains which channel changes cannot be undone.
Archive Teams and Folders in Microsoft Teams
Instructions for archiving a Microsoft Team so its conversations and files become read-only, restoring an archived Team, and making specific SharePoint folders read-only when a whole Team cannot be archived. Also explains what happens to files in an archived Team and the Microsoft 365 Team expiration policy. Applies to Bowdoin Team owners and members.
Best Practices and Limitations in Teams, SharePoint, and OneDrive
One table collecting the limits that apply to files in Microsoft Teams, SharePoint, and OneDrive at Bowdoin: file size, path length, item counts, sharing link and guest expiration, and how long deleted files are kept. Also covers how to structure Teams and channels, how to name files so they do not fail to sync, how to connect Teams files to your computer, and what happens when a Team goes inactive or someone leaves the College. Applies to Bowdoin students, faculty, and staff.
Create a Microsoft Team
Step-by-step instructions for creating a new team in Microsoft Teams for department or project collaboration and file storage. Covers opening Teams, choosing a template and privacy setting, naming the team, adding members and assigning roles, setting up channels, and customizing the team. Applies to Bowdoin students, faculty, and staff.
Files in Microsoft Teams: Start Here
This article is the starting point for anyone working with files in Microsoft Teams at Bowdoin, and it points to the knowledge base article that covers each task. It contains no procedures of its own, and every article it names is listed in the Related Articles section.
Files You Share in a Chat Are Not in the Channel
This article explains that a file attached to a Microsoft Teams chat is stored in the sender's own OneDrive and shared only with the people in that conversation, while a file posted in a channel is stored in the team's SharePoint library and is available to everyone with access to the channel. It covers how to tell the two apart, where meeting recordings are saved, and how to move a chat file into a channel.
Manage and Clean Up Department Files Before the Teams Migration
Best-practice guidance for departments reviewing and cleaning up shared network department drives as part of a migration to Microsoft Teams. Covers using the folder inventory spreadsheet, prioritizing large and old content, applying retention guidelines, handling sensitive data, and building a simple cleanup action plan.
Rename a Team, Channel, or Site
This article explains what changes and what stays the same when a Microsoft Team or one of its channels is renamed. It covers why the SharePoint web address keeps the old name, what other people notice afterward, and the order a Team owner should work in.
See and Restore an Earlier Version of a File
This article explains how version history works for files stored in Microsoft Teams, SharePoint, and OneDrive, where to find it, and how to put an earlier version of a file back. It also explains why restoring an older version does not erase newer ones.
Transition Department Files to Microsoft Teams
A step-by-step guide for departments moving shared files from the Microwave department drive (J:) to Microsoft Teams, in partnership with the Service Desk. Covers requesting help, designing a Team structure, reviewing and grouping files by destination, and completing the transition.
Understand Files in OneDrive, Teams and SharePoint
Explains how OneDrive, Microsoft Teams, and SharePoint fit together, where a file actually lives depending on whether you put it in OneDrive, a Teams chat, or a Teams channel, and how to decide where your own work belongs. Points to the step-by-step articles for moving files and for reaching them from File Explorer or Finder.
Understand Microsoft Teams: Channels, Permissions, and File Structure
An explanation of how Microsoft Teams organizes work into channels, how permissions work across teams and channels, and where files are stored in the linked SharePoint site. Covers standard, private, and shared channels, owner and member roles, the folder structure behind Teams, managing channel settings, and best practices. Applies to Bowdoin students, faculty, and staff.
Using Metadata and Tags with Files in Microsoft Teams and SharePoint
Explains how to use metadata columns to organize and find files in a Microsoft Teams channel, and how to create and use tags to @mention a group of team members. Covers adding metadata in grid view and managing tags for a team.
Using the File Review Spreadsheet to Organize Your Department Files
This article is for department staff who have been asked to review their shared drive content as part of the migration to Microsoft Teams. The File Review spreadsheet is provided by Bowdoin IT and contains a complete list of your department's files plus a summary view to help guide your decisions
What Not to Move into Teams
This article explains which kinds of files stop working, or lose data, when they are placed in a Microsoft Teams channel. It lists the file types a department should leave out of a migration from the Microwave (J:) drive and names where each type belongs instead.