Step-by-Step Tutorial: How to Move Emails from Public Folders to SharePoint

Public folders did their job for a long time: a shared place for departmental emails, calendars, and “team inbox” style workflows. But they were never designed for modern information governance, granular access control, or cross-team collaboration at scale. SharePoint, on the other hand, is built for structured content management: permissions, metadata, retention, search, and collaboration. Using Konnect eMail Central for modern email governance makes this process seamless.

This tutorial is written for Microsoft 365 / Exchange administrators and IT teams planning to migrate shared email history out of public folders into SharePoint as a governed, searchable repository.

Public folders vs SharePoint: what changes in practice?

Here’s the key mindset shift:

• Public folder = shared mailbox-like storage in Outlook
• SharePoint = governed content repository with structure, search, and lifecycle controls

So the goal of this migration usually isn’t to recreate an “inbox experience” in SharePoint. The goal is to move email records and knowledge into a place that’s easier to govern, find, and share.

Preparation for Migration

Assessing current data

Before you move anything, do an inventory. A public folder hierarchy often includes:

• Outdated threads, duplicates, auto-notifications
• Legacy folders nobody owns
• Data that should be archived, not migrated

A practical approach:

• Identify the business-critical folders (used, referenced, audited)
• Define what gets archived vs migrated
• Set a cutoff date where it makes sense (for example: migrate the last 3–7 years, archive older content)

Accessibility and permissions

Permissions are where many migrations fail quietly.

Do this upfront:

• Document who has access to each key public folder (owners, editors, viewers)
• Decide the target model in SharePoint:
  • Site Owners (control)
  • Members (edit)
  • Visitors (read)
• Map access groups to Microsoft 365 or SharePoint groups wherever possible

This is also the right time to decide whether you want:

• Folder-based security (simple but can get messy), or
• Metadata + library-level design (cleaner, more scalable for long-term governance)

Back up existing emails

Even if you use a migration tool, keep a rollback option.

Common backup options include:

• Exporting content to PST for reference and recovery
• Keeping an archival copy in a controlled storage location with documented access

Your goal: if anything goes wrong, you should be able to prove what existed before migration and restore it.

Moving Emails to SharePoint

Choosing migration tools

There’s no single “best” approach. The right method depends on volume, compliance requirements, and how much structure you need to preserve.

Option A: Manual export + upload (small volumes)

Best when:

• You have a small number of folders or limited email history to move
• You’re doing a one-time cleanup of a narrow area

Trade-offs:

• Time-consuming
• Easy to lose searchable context unless you structure and label the content carefully

Option B: Automation for ongoing capture (useful for future-proofing)

Best when:

• You want to capture emails going forward (and optionally selected historic sets)
• You need repeatable, standardized filing patterns

Trade-offs:

• Often needs careful design to avoid dumping “everything” into one library
• Requires a disciplined convention (what gets filed, where, and by whom)

Option C: Compliance-led export workflows (for regulated teams)

Best when:

• Migration is part of a governance/compliance project
• You need defensible export processes for audit or legal requirements

Trade-offs:

• More steps and tighter controls
• Typically requires more IT and compliance coordination

Option D: Third-party migration tools (large volumes + reporting)

Best when:

• You need to migrate a lot of content
• You want mapping, automation, reporting, and error logs

Trade-offs:

• Licensing cost
• Requires a strong plan for what the end-state structure should be

Step-by-step migration process

Step 1: Identify source folders and scope

List the public folders to migrate and define:

• Date range (all-time vs last X years)
• Content types (emails only vs emails + attachments)
• Retention needs (how long this data should be kept)

Step 2: Design your SharePoint destination

Create (or select) the target:

• SharePoint site (Department site, Operations site, Case/Client site)
• Document library (for example: “Email Records” or “Shared Inbox Archive”)

Decide how you want to organize content:

• Folder structure mirroring public folders (simple and familiar), or
• Metadata-driven organization (better long-term scalability)

If you choose metadata, useful columns include:

• Sender
• Recipient(s) or mailbox/team
• Subject
• Sent/Received date
• Client/Project/Case ID
• Category (Billing, Contracts, Support, HR, etc.)
• Sensitivity/Confidentiality

Step 3: Validate permissions before moving data

Confirm who should have:

• Full control (owners)
• Edit access (contributors)
• Read access (viewers)

If sensitive, consider separate libraries or separate sites with stricter access.

Step 4: Run a pilot migration

Pick one representative folder and migrate it end-to-end.

Validate what is preserved:

• Attachments open correctly
• File naming is consistent
• Email headers/metadata are still accessible (as needed)
• Folder placement or tags make sense
• Search works (subject, sender, keywords)

Step 5: Execute the full migration

The exact steps vary by tool, but the structure is consistent:

1. Connect source (public folders) and destination (SharePoint)
2. Select source folders
3. Select SharePoint site + library
4. Map folders and/or metadata fields
5. Run migration with logs enabled
6. Review errors and re-run failed items
7. Run a final delta sync (optional) if the public folder remained active during the migration window

Step 6: Preserve structure without recreating chaos

A practical compromise that works well:

• Preserve the top-level folder structure users recognize
• Reduce deep nesting by using:
  • metadata columns
  • views (“By Client”, “By Project”, “By Year”, “By Category”)

This keeps the experience familiar while preventing the same public-folder sprawl from being rebuilt in SharePoint.

Post-Migration Considerations

Verifying migration success

Don’t rely on a “completed” message. Validate with evidence.

A solid verification checklist:

• Item counts: source vs destination (per folder)
• Attachment sampling: open a random sample across folders
• Search validation: find emails by sender/subject/date keywords
• Permissions check: confirm the right users have the right access
• Exception log review: identify skipped, failed, or partial items

Create a short internal record of the results (what was migrated, when, where it lives now, and who owns it).

Training users on the new workflow

Even a perfect technical migration fails if users don’t adopt it.

Keep training short and workflow-based:

• Where the migrated emails live (site + library)
• How to find content (search, views, filters, metadata)
• What to do going forward (how new emails should be saved and categorized)
• Who to contact for access or filing issues

Conclusion

Moving emails from public folders to SharePoint is not just a storage change. It’s a governance upgrade: clearer access control, stronger collaboration, and a structure that supports retention and discovery.

If you follow the sequence (assess → permission map → pilot → migrate → verify → train), you’ll avoid the two classic failures: moving everything without structure, or moving the structure without user adoption.

If you also want to make it easier for teams to consistently save emails into the right SharePoint location directly from Outlook (without relying on manual drag-and-drop or inconsistent naming), Konnect eMail is often used as the enablement layer after or alongside the migration, so the new system stays clean and usable long-term.

Konnect eMail also provides a migration tool designed to help organizations seamlessly move emails stored in Exchange Public Folders into SharePoint for improved accessibility, governance, and long-term management. The tool securely extracts emails from Exchange Public Folders, preserves their content, and saves them as files in SharePoint libraries while optionally replicating the original Public Folder structure to maintain familiarity and organization. Konnect Email also allows users to define custom naming conventions for the email files, ensuring consistency and alignment with organizational standards. During migration, key email properties—such as sender, recipients, subject, and sent or received dates—are captured and stored as SharePoint metadata, enabling powerful search, filtering, and compliance capabilities within SharePoint.