SharePoint cross-site file move notifications and user alert behavior

Avery Noleroth (avnolero) 0 Reputation points
2026-09-30T16:44:38.5133333+00:00

Hi everyone, our team is preparing to migrate our content from an older SharePoint site to a newly organized site with updated structure and stricter library permissions. As we plan the transition, we want to be proactive about user experience and avoid any unexpected noise. When files and folders are moved between sites, do document creators, original owners, collaborators, or site members or owners receive any automated system notifications or email alerts? We’d love to understand if there are specific scenarios where alerts might get triggered and any best practices you recommend for keeping the move smooth and silent for end users.

Microsoft 365 and Office | SharePoint | Development
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Lin v 1,545 Reputation points Independent Advisor
    2026-09-30T17:13:14.7933333+00:00

    Hi Avery,

    The exact behavior can depend on whether you're using SharePoint Online or an on-premises version of SharePoint, as well as any custom workflows, alerts, or third-party solutions configured in your environment.

    Generally speaking, moving files between libraries or sites does not by itself generate automatic email notifications to document creators, collaborators, site members, or site owners. However, notifications may occur if there are existing alerts, automation rules, workflows, or custom processes configured on the source or destination locations.

    To help minimize unexpected notifications during the migration, you may want to review any alerts, Power Automate flows, workflows, or other automation associated with the affected libraries before performing the move. For reference: Create an alert to get notified when a file or folder changes in SharePoint

    In most standard SharePoint Online file move scenarios, users should not receive automatic email notifications solely because content was moved between sites. I hope this information is helpful.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-09-30T16:44:53.8133333+00:00

    Moving behavior and notification behavior differ by scenario:

    • Move within the same SharePoint site: the file is simply relocated. It keeps its identity and version history, and no deletion event is triggered. In that case, it does not appear in the site Recycle Bin.
    • Move from one SharePoint site to another site: SharePoint creates a new copy in the destination site and then removes the original from the source site. From the source site’s perspective, this is treated as a true delete operation, so the original is placed in the source site Recycle Bin.

    For alerts and notifications:

    • SharePoint supports alerts on a list, library, folder, file, or list item.
    • A user can set an alert for a specific folder or file, not just the whole library.
    • Alerts are designed to notify when an item changes, and notifications can take up to 4 hours to arrive.
    • Because cross-site moves are handled as a new copy in the destination plus deletion from the source, users who already have alerts configured on the affected source or destination content may receive alert activity related to those changes.
    • Alerts are not a good long-term dependency for this migration planning because SharePoint Alerts in Microsoft 365 are being retired. Microsoft recommends using rules or Power Automate for notification scenarios.

    Best practices for a smoother, quieter migration:

    1. Assume existing alerts may create noise if users have alerts on source libraries, folders, files, or items.
    2. Communicate before and after migration so users understand that content changes may generate notifications and that alerts generally do not migrate to the new environment.
    3. Plan to recreate only required notifications in the new site, because basic migration tools generally do not migrate alerts.
    4. For modern notification scenarios in the new site, prefer SharePoint Rules or Power Automate instead of relying on classic alerts.
    5. If preserving metadata matters, review destination library differences carefully: when moving or copying to a location with different properties, only supported properties at the new location are maintained.
    6. If using Move to between libraries, be aware that SharePoint warns when the destination has a lower version limit and versions could be lost.

    What is supported by the available information:

    • There is support for item-change alerts.
    • Cross-site moves are treated differently from same-site moves.
    • Alerts may exist at multiple scopes and can therefore be triggered by content changes.
    • Alerts do not generally migrate with content migration tools.

    What is not established here:

    • There is no supported statement here that SharePoint automatically emails document creators, original owners, collaborators, site members, or site owners by default just because a move occurred. The documented notification mechanism is user-configured alerts, plus newer rules or Power Automate.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.