EN
ES
DE
FR
NL
IT
JA
PT
PL
KO
SmartMapper for ReplaceMagic is aimed at large, complex migration projects — SharePoint tenant-to-tenant moves, on-prem to SharePoint Online, server consolidations, and any scenario where the source environment contains thousands of links that nobody wants to translate by hand.
Traditional ReplaceMagic editions ask you to provide the search/replace pairs. SmartMapper inverts that workflow: you provide simple Source → Target mapping rules, and SmartMapper figures out the rest. Only patterns you explicitly accept are ever applied to your documents.
How SmartMapper fits your migration workflow
[1]
ReplaceMagic
Scanner
Scanner
Scans your documents; populates hyperlinks, OLE, link sources, Power Queries
→
[2]
SmartMapper
(this product)
(this product)
Resolves links → applies mapping rules → generates confidence-scored search/replace patterns
→
[3]
You Review
Accept, modify or reject each pattern. Only approved patterns proceed.
→
[4]
Replacement
Engine
Engine
Applies accepted patterns to real documents. Zero guesswork.
For each link discovered during a scan, SmartMapper: detects the link type (Absolute, Relative, SharePointDocID, OneDriveID, PowerQuery, ConnectionString, OneNote, SharePoint-special); resolves it; compares the resolved link against your mapping rules and produces the NewLink; derives the minimal SearchString / ReplaceString pair from OriginalLink and NewLink; and consolidates redundant patterns while flagging conflicts for human review. The output is a reviewable table of patterns — each with a confidence score and an audit trail.
The SmartMapper Engine — What's New vs. Ultimate
Automatic pattern generation
- Define mapping rules, not search/replace pairs
- SmartMapper consolidates redundant sub-folder patterns into one rule
Link resolution & extraction
- Relative will be resolved and scoped to the document containing the link
- SharePoint, OneDrive ID-based links
- Extracts links from PowerQuery commands (
File.Contents,Folder.Files,SharePoint.Files,Web.Contents…) - Extracts links from connection strings (
Provider=,DSN=,Data Source=,OPENROWSET,OPENDATASOURCE,BULK) - Handles SharePoint specials (
../../:f:/r/Folder),file:,onenote:andjavascript:URIs
Validation before execution
- SmartMapper simulates every pattern against every resolved link
- Reports per pattern: correct, unchanged, incorrect
- Per-pattern confidence
- Run-level accuracy and coverage reported separately — never blended into one score
Review workflow & governance
- Every pattern carries a status: Generated, Accepted, Rejected, Modified, Conflict
- Conflict groups flag identical SearchStrings with different ReplaceStrings for human review
- Folder-context-aware patterns handle identical relative links resolving to different targets
- Nothing runs against your documents until you approve it
- Original and modified SearchString/ReplaceString are both stored for audit
Cloud-aware rewriting
- PowerQuery rewriting:
File.Contents→Web.Contents/SharePoint.Fileswhen targets are in the cloud - Strips
file:prefix when the destination is SharePoint - Preserves SharePoint URL parameters as unique pattern combinations
Pick the backend that fits
- SQL Server for shared, enterprise-governed projects
- SQLite for laptop / partner-led projects — one file, zero install, no licence
- MySQL as an alternative open-source relational backend
- Identical schema and identical results — verified at scale (400,000+ keys, 99%+ confidence on 12M+ source rows)
Supported File Formats
- Microsoft Word — .doc, .dot, .docx, .dotx, .docm, .dotm
- Microsoft Excel — .xls, .xlt, .xlw, .xla, .xlsx, .xlsm, .xlsb, .xltx, .xltm
- Microsoft PowerPoint — .ppt, .pps, .pot, .pptx, .pptm, .potx, .potm, .ppsx, .ppsm
- Microsoft Visio — .vdx, .vsdx, .vssx, .vstx
- Microsoft Project — .mpp, .mpt
- Microsoft OneNote — .one [BETA]
- Adobe PDF — .pdf
- Text files — .txt, .csv, .html, custom extensions
- Windows Shortcuts — .lnk
- SharePoint Canvas & Wiki pages — .aspx
Document Areas Processed
- Hyperlinks (web URLs and file paths)
- OLE Object links
- Link Sources (Excel & Word external references)
- Power Queries & Pivot references (Excel)
- VBA code references
- Excel Connections
- Footnotes (Word)
- Comments & Field Codes
- Headers and Footers
- Plain text body content
- SharePoint Canvas & Wiki content
Typical Inputs — What You Provide
- A list of folders and/or SharePoint sites to scan
- Mapping rules — one row per source-to-target pair, for example:
\\ServerABC\Finance→https://company.sharepoint.com/sites/financenew
\\OldServer\HR→https://company.sharepoint.com/sites/hr - A review of the auto-generated patterns — accept, modify, or reject
A Concrete Example — What Happens to One Link
Trace: one relative link through the full SmartMapper pipeline
| Document being scanned | \\ServerABC\Finance\Reports\Q2.xlsx |
| Raw link found inside it | ..\Sub1\file.xlsx |
| Your mapping rule | \\ServerABC\Finance → https://company.sharepoint.com/sites/financenew |
What SmartMapper does:
- Detects link type: Relative
- Resolves to it
- Applies mapping rule → NewLink:
https://company.sharepoint.com/sites/financenew/Sub1/file.xlsx - Simulates the pattern against all links → reports correct / incorrect count + confidence score
- You review the pattern and click Accept. Only then does the replacement engine touch Q2.xlsx.
Common Use Cases
- SharePoint Online migration with thousands of relative and ID-based links — SmartMapper resolves them all without hand-mapping
- SharePoint tenant-to-tenant migration with ID-based links — when you move to a new tenant, old
DocID,OrganizationalViewLinkandDirectLinkURLs become dead because those IDs simply do not exist in the new tenant. SmartMapper scans the source tenant’s document index before migration while the IDs are still resolvable, resolves them, and produces search/replace patterns that work correctly even after the source tenant is decommissioned and the IDs are gone. No conventional search/replace tool can do this because IDs are meaningless the moment the source goes offline. - File share to SharePoint / OneDrive — UNC and mapped-drive paths converted to cloud URLs in one pass
- Server consolidation with overlapping folder structures — conflict detection flags ambiguous mappings before they cause damage
- Migration to Google Drive, Box, Dropbox — links repaired across the move to the new cloud location
- Excel-heavy estates with PowerQuery, Pivot caches, OLE links and ConnectionString-embedded paths — SmartMapper extracts the link from the surrounding string and rewrites it correctly
- Audit and dry-run before go-live — validation reports correct / incorrect counts so the project owner can sign off on a number, not a hope
- Multi-wave migrations — every run scoped by RunID so multiple waves can coexist in the same SmartMapper database without contaminating each other
Is SmartMapper Right for You?
You need SmartMapper if…
- Your migration involves hundreds or thousands of documents
- You have ID-based SharePoint / OneDrive / cloud links that UNC search-replace can’t touch — especially tenant-to-tenant moves where the old DocIDs will not exist in the new tenant (SmartMapper resolves them before the source goes offline)
- Your Excel workbooks use PowerQuery, Pivot or ConnectionString data sources
- You need a sign-off report showing how many links will be fixed before go-live
- You are a migration partner running projects for multiple clients
- You have overlapping folder structures where the same relative path resolves differently
- You need an auditable record of every change for compliance
Consider Ultimate or a single-edition instead if…
- You already know your exact search and replace strings
- Your migration is a simple server rename with straightforward UNC paths
- You are fixing links in one specific file format only (e.g. Word only)
- Budget is a constraint and the project is small-scale
Not sure? Compare all editions or ask us — we’ll tell you honestly.
Proven at enterprise scale
Verified on a production-scale run of 12+ million source rows across 900,000+ documents:
400,000+ search/replace keys generated • 99%+ confidence • 96%+ coverage.
400,000+ search/replace keys generated • 99%+ confidence • 96%+ coverage.
Why Choose SmartMapper for ReplaceMagic?
- You stop writing search/replace pairs. Define the migration in business terms (source → target) and let SmartMapper generate the technical patterns.
- You know the outcome before you commit. Per-pattern accuracy, run-level accuracy and coverage as two separate figures, and explicit correct / incorrect counts replace guesswork with numbers.
- You catch the dangerous edge cases automatically. Conflict groups and folder-context-specific patterns prevent the silent wrong-replacement that ruins migration weekends.
- You handle the links other tools ignore. ID-based SharePoint / OneDrive URLs, PowerQuery
File.Contents, ConnectionStringData Source=, OneNoteonenote:paths — all resolved and remapped. - You ship a reviewable artefact. The generated patterns table is an auditable record of every change — original pattern, modified pattern (if any), status, source table, link type — for security and compliance sign-off.
- Full ReplaceMagic.Ultimate included. Every format and every link area covered by Ultimate is part of SmartMapper — you don't trade coverage for intelligence.
- Recommended for migration partners, IT integrators and enterprise IT teams running projects where hand-crafted patterns are not an option.
SmartMapper engine features:
Supported extensions:
Microsoft Word-Document (*.doc,*.dot,*.docx,*.dotx,*.docm,*.dotm)
Microsoft Excel-Document (*.xls,*.xlt,*.xlw,*.xla,*.xlsx,*.xlsm,*.xlsb,*.xltx,*.xltm)
Microsoft PowerPoint-Presentation (*.ppt,*.pps,*.pot,*.pptx,*.pptm,*.potx,*.potm,*.ppsx,*.ppsm)
Microsoft Project-Document (*.mpp,*.mpt)
Microsoft Visio Drawing (*.vdx,*.vsdx,*.vssx,*.vstx)
Microsoft OneNote (*.one)
Adobe PDF (*.pdf)
Text documents (*.txt, *.csv, *.html but also your custom extensions)
Windows Shortcuts (*.lnk)
SharePoint Canvas and SharePoint Wiki pages (*.aspx)
Supported Office versions: 2000-2013 and most of the features in 2016/2019/Office 365
Requirements: .NET Framework 4.8 or higher.
Database backend — choose what fits the project:
• SQL Server (default) — Express edition is sufficient; recommended for shared, multi-user, enterprise-governed projects.
• SQLite — a single database file, zero install, no service, no licence. Ideal for smaller customers or migration partners who run projects on a laptop without a SQL Server in reach.
• MySQL — open-source relational backend for organisations that standardise on MySQL infrastructure.
All three backends share the same schema and produce identical results — verified at scale on a production-scale run of 12M+ source rows (~9M derived rows): both produced 400,000+ search/replace keys across 900,000+ documents with 99%+ confidence, 96%+ coverage.
- Mapping-rule-driven workflow — provide Source → Target pairs, not search/replace pairs
- Link type detection: Absolute, Relative, SharePointDocID, OneDriveID, UnknownID
- Relative-to-absolute resolution scoped to the file containing the link
- ID-based link resolution against the document index (docID, DocIdUrl, DirectLink, OrganizationalViewLink/EditLink, AnonymousViewLink/EditLink)
- link extraction for long strings: PowerQuery commands, ConnectionString fragments (Provider=, DSN=, Data Source=, DBQ=, DefaultDir=, Location=, Database=, URL=),
<LISTWEB>/<ROOTWEB>, OPENROWSET, OPENDATASOURCE, BULK - PowerQuery command rewriting (File.Contents → Web.Contents / SharePoint.Files / SharePoint.Contents) for cloud targets
- SharePoint URL specifics preserved (
../../:f:/r/Folder,onenote:,file:) - Auto-generated SearchString/ReplaceString
- pattern consolidation merges redundant patterns sharing a common parent
- SmartMapper simulates replacements and reports correct, unchanged, incorrect
- Per-pattern accuracy, plus run-level accuracy and coverage reported as two independent figures
- Pattern statuses: Generated, Accepted, Rejected, Modified, Conflict
- RunID-scoped operation — multiple migration waves coexist without contamination
- Persistent unresolved links table with reason codes for full auditability
- Backed by SQL Server — results survive the run and can feed BI / sign-off reporting
- Search and replace inside the headers and footers of multiple sections
- Search and replace inside hyperlinks and hyperlink addresses
- Search and replace UNC link paths
- Search Only mode - very handy for detecting where replaces would occur
- Search and replace international character sets
- Handles any number of sub folders
- Handles documents with password for open or modify
- Easy to install/uninstall
- The original file date and time stamp will be preserved.
Supported extensions:
Microsoft Word-Document (*.doc,*.dot,*.docx,*.dotx,*.docm,*.dotm)
Microsoft Excel-Document (*.xls,*.xlt,*.xlw,*.xla,*.xlsx,*.xlsm,*.xlsb,*.xltx,*.xltm)
Microsoft PowerPoint-Presentation (*.ppt,*.pps,*.pot,*.pptx,*.pptm,*.potx,*.potm,*.ppsx,*.ppsm)
Microsoft Project-Document (*.mpp,*.mpt)
Microsoft Visio Drawing (*.vdx,*.vsdx,*.vssx,*.vstx)
Microsoft OneNote (*.one)
Adobe PDF (*.pdf)
Text documents (*.txt, *.csv, *.html but also your custom extensions)
Windows Shortcuts (*.lnk)
SharePoint Canvas and SharePoint Wiki pages (*.aspx)
Supported Office versions: 2000-2013 and most of the features in 2016/2019/Office 365
Requirements: .NET Framework 4.8 or higher.
Database backend — choose what fits the project:
• SQL Server (default) — Express edition is sufficient; recommended for shared, multi-user, enterprise-governed projects.
• SQLite — a single database file, zero install, no service, no licence. Ideal for smaller customers or migration partners who run projects on a laptop without a SQL Server in reach.
• MySQL — open-source relational backend for organisations that standardise on MySQL infrastructure.
All three backends share the same schema and produce identical results — verified at scale on a production-scale run of 12M+ source rows (~9M derived rows): both produced 400,000+ search/replace keys across 900,000+ documents with 99%+ confidence, 96%+ coverage.
