How to Merge Document Changes in SharePoint
When two people edit a document separately, you eventually need to merge their changes into one clean version. Done well, this is structured. Done badly, it’s chaos.
What it is
Document merging happens when collaboration breaks the co-authoring model. Maybe two people edited offline, two versions diverged because someone downloaded a copy, or two contributors worked on different sections of the same document independently. Whatever the cause, you end up with two (or more) versions and need to combine them into one.
Word’s Compare feature can help with this: produce a diff, then manually reconcile differences. For more structured merging, Word also has a Combine option specifically for merging tracked-changes versions from multiple reviewers. For complex documents with many divergences, sometimes the cleanest solution is to identify a primary version and manually port changes from the other version into it.
The real lesson, though, is that merging is a symptom of a broken collaboration workflow. If you’re merging documents regularly, the team is working in parallel when they should be co-authoring. The best fix isn’t getting better at merging — it’s making sure everyone works from one shared cloud version with co-authoring on, so divergence never happens in the first place.
When to use this
- When two people have edited the same document offline and you need to combine their changes.
- When a document was downloaded by mistake and edited locally, and the cloud version has also been updated.
- When you’re consolidating tracked-changes reviews from multiple reviewers.
- When you’ve inherited a project with several divergent draft versions.
How to do it
- Identify all the versions that need merging and the source of truth.
- Use Word’s Compare tool to see differences between versions.
- For tracked-changes merging, use Review → Compare → Combine.
- Walk through each difference and decide: keep, replace, or merge.
- Resolve conflicts where the same section has been changed differently in both versions.
- Save the merged document as the latest version in the official location.
- Add a check-in comment describing the merge.
- Notify contributors that the merged version is the source of truth from now on.
Best practices
- Prevent merging by enforcing co-authoring. One cloud file, multiple editors. No download-edit-upload cycles.
- One person owns the merge. Distributed merging causes new divergence.
- Use comments to capture decisions. ‘Kept Sarah’s version of section 3 because it reflects updated policy.’
- After merge, retire the divergent versions. One source of truth from this point forward.
Common mistakes
- Merging in parallel. Two people independently merging the same documents creates a third divergent version.
- Not communicating after merge. Contributors keep editing their old versions because they don’t know there’s a merged source of truth.
- Skipping documentation. Six months later, nobody remembers why a particular merge decision was made.
The SharePoint Essentials System is the most comprehensive end-user guide in the range. 7 modules, 35 slides covering navigation, libraries, views, lists, metadata, permissions, and decision trees — updated for the new 2026 SharePoint App Bar.
Get the Essentials System — $37 →FAQ
How do I merge changes from two SharePoint Word documents?
Open one document in Word desktop. Click Review -> Compare -> Combine. Choose the second document. Word produces a merged document with all changes from both originals visible as tracked changes. Accept or reject each change to produce the final merged version. Save back to SharePoint.
What’s the difference between Combine and Compare in Word?
Compare shows differences but produces a read-only result for review. Combine merges the documents into a single editable document with all changes consolidated. Use Compare for review and analysis; use Combine when you need to produce a final merged document.
How does SharePoint co-authoring handle merge conflicts?
Co-authoring resolves most conflicts automatically — edits to different parts of the document combine seamlessly. For conflicting edits to the same paragraph, Word shows both versions and lets the last editor choose. The model is ‘last writer wins with visibility’, not silent overwrite. Real conflicts are rare in practice.
Should I co-author or merge versions in SharePoint?
Co-author whenever possible — it’s faster, lower-friction, and avoids merge complexity. Use Combine only when parallel editing wasn’t possible (e.g. someone was offline, or two teams worked separately and you need to consolidate). Co-authoring is the default; merging is the exception.