Known SharePoint Limitations When Using ReplaceMagic

ReplaceMagic is designed to handle the full complexity of SharePoint document processing, but like any tool that operates within a platform built by another vendor, it is subject to certain constraints. The limitations documented on this page are either imposed by SharePoint itself, by the Windows operating system, or by the Office file format specifications. Understanding these boundaries before you start a large migration project will help you plan effectively and avoid surprises.

Group 1: File and Path Limitations

• Special characters in file names — Files whose names contain any of the following characters cannot have their shared link tokens or organizational links retrieved via the SharePoint API: ~ # % & * { } \ : <> ? / + | ". These files are still downloaded, processed for broken links in their content, and re-uploaded — but shared-link-style URLs that reference the file by token cannot be repaired. This is a limitation of the SharePoint REST API, not of ReplaceMagic.
• Windows path length limit (260 characters) — When ReplaceMagic downloads files from SharePoint to a temporary local path for processing, the combined length of the temporary folder path and the file name must not exceed 260 characters. A workaround is available in the ReplaceMagic Processing settings: enable long path support or shorten the temporary folder path to a root-level directory such as C:\Temp.
• Excel link source path length — Excel enforces maximum path lengths on external link sources. In older Excel formats (.xls), the maximum path length for a link source is 253 characters. In newer formats (.xlsx, .xlsm), the limit is 2,000 characters. If a replacement would produce a URL or file path that exceeds these limits, ReplaceMagic skips the specific link and logs it in the results report. The document itself is still processed; only the oversized link is skipped.

Group 2: SharePoint Platform Limitations

• SharePoint list view threshold (5,000 items) — SharePoint Online and on-premises both enforce a maximum of 5,000 items per list query. ReplaceMagic uses a default query row limit of 4,900 to stay safely below this threshold. If you reduce this value in the SharePoint Configuration tab, queries will be smaller and safer but will also take longer to enumerate large libraries.
• Maximum document ID (30,000,000) — When resolving ID-based SharePoint links, ReplaceMagic iterates through document IDs up to the configured maximum. The default of 30,000,000 matches SharePoint’s practical upper limit. If your tenant has documents with IDs above this value (unusual but possible in very large, long-lived tenants), increase the Max Doc ID setting in configuration.
• SharePoint throttling (HTTP 429 / 503) — SharePoint Online enforces rate limiting on API requests. ReplaceMagic detects throttling responses and retries automatically, but sustained high-parallelism processing will still encounter throttling delays. The recommended thread count for SharePoint Online is 3–5. Using more threads does not proportionally increase throughput on SharePoint Online because throttling increasingly offsets the gains.
• Modern authentication requirement — Tenant administrators can disable legacy authentication protocols in Microsoft 365, which means username/password and app-password login methods may not function. In this case, use App-Only Authentication with an Azure AD application registration. App-Only Authentication is not subject to legacy authentication restrictions.

Group 3: Metadata and Versioning

• Preserving last-modified date and author requires Site Administrator rights — ReplaceMagic uses a privileged SharePoint API call to restore the original editor and modification timestamp. This call is only available to accounts with Site Administrator (Site Collection Administrator) rights. Contributor or Member permissions are not sufficient. If the processing account has only contributor rights, the modified-by field will show the processing account and the modification date will be set to the time of processing.
• Document backup is not available in native SharePoint mode — ReplaceMagic’s built-in file backup feature (which copies originals to a backup folder before modification) does not function when processing documents natively through the SharePoint API. Use SharePoint’s built-in version history as your safety net. Ensure that versioning is enabled on the target library before running a processing job.
• Content approval preservation requires appropriate rights — Restoring the content approval status of a document after processing requires that the processing account has permission to approve and reject items in the library. Without approval rights, ReplaceMagic will complete the content modification but will not be able to restore the approval status.

Group 4: Connectivity

• On-premises network access required — For SharePoint on-premises, ReplaceMagic must be installed on a machine that can reach the SharePoint server over the network. The machine must be able to resolve the SharePoint server’s hostname via DNS and connect to it on the appropriate HTTP or HTTPS port. No components are installed on the SharePoint server itself, but network line-of-sight is mandatory.
• Corporate proxies and firewalls — If your organization routes outbound HTTPS traffic through a corporate proxy or firewall, connections from ReplaceMagic to SharePoint Online may be blocked or require proxy authentication. Configure the proxy settings in the ReplaceMagic Processing settings panel. If SSL inspection is enabled on the proxy, the SharePoint Online certificates may appear invalid — coordinate with your network team to add the necessary exceptions.

These limitations are documented to help you plan your migration project accurately. If you encounter a specific scenario not described here, please contact us at support@replacemagic.com and we will be happy to advise.