REGEXREPLACE changes every matching instance in its input. A pattern that is too broad can remove meaningful content even when the resulting strings look cleaner.
Retain the source and define the target
Write down the precise transformation. For example, removing the literal prefix ID- at the beginning is different from removing those characters anywhere in a record.
Test =REGEXREPLACE(A2,"^ID-","") in a helper column. The caret anchors the match to the beginning, so an ID- sequence in the middle is not removed by this pattern.
Avoid unnecessarily broad expressions
A dot or repetition operator can span more text than intended. Use explicit character sets and boundaries when the source structure permits them. If you only need a literal text replacement, SUBSTITUTE may communicate the task more clearly.
Sheets uses RE2 with its documented limitations. A pattern copied from another engine may not be supported or may represent a different assumption. Do not apply an untested cleanup expression directly over the only copy of the source.
Test records that should remain unchanged
Include valid prefixes, similar internal text, blank inputs, punctuation, and non-ASCII characters from the actual dataset. Compare original and transformed values side by side. Count changed records and inspect unexpected changes.
Check for collisions where different originals become the same cleaned value. A replacement suitable for display labels may be unsafe for account keys. Keep a documented exception path and retain originals through reconciliation. Only replace working data after the exact transformation, its scope, and its effect on downstream lookups have been reviewed against representative examples.
References
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.