Reading the results
At the end of a run SmartMapper prints a summary:
Resolved=16611 Mapped=12093 WouldFix=12093 WouldBreak=0
>>> Coverage (in-scope fixed) = 81,13%
Patterns (SearchReplaceKeys): 9.248
|
Figure |
Meaning |
|
Resolved |
Links turned into a complete address |
|
Mapped |
Links a rule could convert |
|
Patterns |
Search/Replace keys generated |
|
WouldFix |
Links the keys will repair |
|
WouldBreak |
Links the keys would damage – should be 0 |
|
Coverage |
Share of in-scope links that will be repaired |
|
Confidence |
Overall quality indicator for the key set |
Why links may remain unmapped
|
Reason |
Meaning |
What to do |
|
NoMappingRules |
The location is in scope but no rule describes it |
Add a rule (use Suggest rules / Coverage gaps) |
|
External |
The link points outside the migration (internet, other systems) |
Nothing – correct behaviour |
|
IDMatchNotFound |
An ID link whose target document is not in the scan |
Widen the scan, or see Where to scan if you scanned at the target |
|
SameFolderLink |
A short link that does not need or cannot get conversion |
Nothing, unless a rule for that folder is missing |
|
SharingTokenUnresolved |
A sharing link whose token matches nothing in the scan |
Widen the scan to include the linked content, or re-share the item at the target |
|
Internal |
Bookmark or cell reference inside the document |
Nothing |
|
UnsupportedType |
mailto:, javascript: and similar |
Nothing |
|
OutsideOfParent |
A relative link pointing above the scanned root |
Widen the scan if those files matter |
A high number of External or Internal entries is normal and does not indicate a problem – coverage is calculated only over the links that are actually in scope.
External links and your rules
SmartMapper does not inherently know what "the internet" is – External simply means no mapping rule covers this link. External links never receive a target address and are never rewritten. Because the classification follows your rules, it is worth skimming the External list once: if a host or file share appears there that is part of your migration, the rule for it is missing – add it and regenerate, and those links will be converted like any others. The same works later: if externally-linked content moves one day, add a rule for it and re-run.