What SmartMapper converts
|
Link type |
Example |
Handling |
|
Absolute path |
\\server\share\Plan.docx |
Mapped by rules |
|
Absolute URL |
http://intranet/hr/Policy.docx |
Mapped by rules |
|
Relative link |
..\Shared\Overview.pptx |
Resolved against the document's folder, then mapped |
|
Same-folder link |
ProjectPlan.docx |
Converted to a full URL – see below |
|
Document-ID link |
.../DocIdRedir.aspx?ID=PGTI-644-4324 |
Resolved through the scanned document inventory (also in relative form) |
|
Sharing link (path form) |
.../:f:/r/Shared Documents/Reports?csf=1 |
The /r/ form carries a real path – converted by rules |
|
Sharing link (token form) |
.../:x:/s/Finance/EUA0mfifgxR... |
Converted when the linked document – or, for folder shares, the folder – is part of the scan |
|
OLE object |
embedded workbook reference |
Mapped like any other link |
|
PivotTable source |
'C:\Data\[Sales.xlsx]Q1'!A1:C11 |
Both the full and the short form are converted |
|
Power Query |
File.Contents("\\srv\data.xlsx") |
Path is mapped; local-file commands become their cloud equivalents when the target is a web location |
|
Connection string |
Provider=...;Data Source=\\srv\db.accdb;... |
The path inside the string is mapped |
Same-folder links deserve special attention
A link that is only a file name – ProjectPlan.docx – works on a file share because Office looks in the same folder. After migration to SharePoint this breaks: Office has no folder context any more and turns the name into an invalid address such as http://ProjectPlan.docx.
SmartMapper therefore converts these into full addresses:
ProjectPlan.docx → https://contoso.sharepoint.com/Shared Documents/Migration/Projects/ProjectPlan.docx
Conditions: the document's folder must be covered by a rule whose target is a web location. If content is only moving from one file share to another, the short form keeps working and is deliberately left untouched.
What cannot be converted
- Sharing links built on an opaque token (/:f:/s/..., /:x:/g/... with a generated ID) – only when the linked content is outside the scan. SmartMapper checks the scan inventory in two ways: if the link's token belongs to a scanned document, it resolves to that document; if the link points at a folder that contains scanned content, it is recognized as a folder link. Both convert correctly. Only when neither check finds the target is the link reported as SharingTokenUnresolved – such tokens were issued by the source system and cannot be decoded, so those items must be re-shared at the target. Widening the scan to include the linked content converts these links too.
- Document-ID links when scanning at the target – see Where to scan.
- Links the scanner cannot see – for example URLs typed as plain text in a cell, or links generated by VBA code.
- Renames the rules do not describe. If the migration renames files or restructures folders in a way your rules do not express, the calculated target address will not match reality.
PivotTable refresh after migration: a converted PivotTable source refreshes correctly in the Excel desktop application. Excel in the browser cannot refresh data from another workbook at all – this is a Microsoft limitation that applies equally before and after migration.