ReplaceMagicHelp

A source scan sees the world exactly as the documents describe it:

• Relative links (..\Shared\Overview.pptx) resolve against the real source folder structure.
• Document-ID links (.../DocIdRedir.aspx?ID=PGTI-644-4324) can be looked up in the scan's own document inventory, because the scan and the IDs come from the same system.
• Sharing links and ordinary absolute links resolve normally.

A source scan also records both addresses for every key – the document's current location and its calculated future location – which means you can apply the repairs either before or after moving the content. See Repair before or after the migration.

When a target scan is acceptable

If the content has already been migrated and the source is no longer available, you can scan at the new location instead. SmartMapper recognises that the documents already sit at their destination and handles them correctly.

Why ID links cannot work in a target scan: the link inside the document carries an identifier issued by the old system, but a scan of the new location can only see the new identifiers, which the migration reassigned. There is no way to connect the two. Those links are reported as IDMatchNotFound.

Documents renamed by the migration. A target scan also avoids a problem of source scans: if the migration tool renamed documents (for example # or % replaced by _), the keys of a source scan point to the old names, and these documents are not processed (ReplaceMagic warns and saves a list, see Repair before or after the migration). A target scan sees the new names. The links inside the documents still point to the old names of the files they link to; for those, use the illegal characters conversion (Configuration -> SharePoint 2) with the same characters that the migration replaced.

How to know whether you have ID links

You do not have to guess. Run SmartMapper and read the report:

• the link-type summary shows how many links were resolved as SharePointID / DocID;
• the unresolved summary shows IDMatchNotFound.

If those numbers are zero, a target scan costs you nothing. If they are significant, they represent exactly the links that only a source scan could have repaired.

What not to do: scanning a staging copy

Copying documents to an intermediate “staging” folder and scanning there is not recommended. Relative links resolve against the staging folder structure, which your mapping rules do not describe, so they cannot be mapped. A staging location is neither the source nor the target, so neither stored address matches it.

Summary