ReplaceMagicHelp

A mapping rule is a pair: Source (where content is now) → Target (where it will be). Rules are stored per RunID.

How rules are matched

• When multiple rules match, ReplaceMagic automatically selects the most appropriate rule based on specificity. This allows you to define broad rules for an entire server alongside more targeted rules for individual libraries, while ensuring that the intended transformation is applied and unexpected changes are avoided.
• Matching ignores upper and lower case.
• Encoded and plain characters are equivalent: a rule written Shared Documents matches a link written Shared%20Documents, and vice versa. The same applies to accented characters and other encoded punctuation.

Practical guidance

• Write folder names exactly as they really are. Shared Documents (with the space) is a different name from SharedDocuments, and the latter will never match.
• Cover the locations where your documents live, not only the locations they link to. This matters if you intend to repair documents after moving them. SmartMapper reports any document whose own location no rule describes.
• Start from the suggestions. The Suggest rules action inspects the unmapped links of a run and proposes rule drafts for the locations that appear most often. The Coverage gaps action lists the locations that are still unmapped, ordered by how many links they affect. Together they turn rule authoring into a short, prioritised checklist.