Understand conflict copies after syncing again
This applies to all four document types when local files move into iCloud or sync resumes and the same document already exists in the cloud. It can happen after you turn sync back on, without a conflict-version panel appearing first.
For example, you turn sync off, keep local files, and continue editing locally. When you enable sync again, iCloud may still hold the original document. Prodrafts compares the two files’ modification times to decide how to move the local file.
Two possible results
| Comparison | Result |
|---|---|
| The local file has a newer modification time | The cloud document stays unchanged. The local version is uploaded as a separate document, so another copy may appear in the library. |
| The local file is older or has the same modification time | The duplicate local copy is removed, and the document is opened from its cloud location. |
This comparison uses file modification times. It does not compare paragraphs to decide which version is more complete, and it does not merge all changes into one document. No extra copy does not, by itself, prove the contents are identical.
Check a new copy before organizing
- Wait for sync to finish and note any errors or incomplete status.
- Open the original and the new copy separately. Compare page counts, key paragraphs, recent handwriting, and attachments, not just names or thumbnails.
- Once both open correctly, export native files or create a backup.
- Decide which document to keep editing. Transfer anything needed from the other copy using the appropriate copy, paste, or page-management tools.
- Check that the combined content is complete before deciding whether to delete an unwanted copy. With sync enabled, deletion also affects iCloud and other devices.
Why no version picker appeared
Creating copies during migration is automatic and differs from the selection panel described in Resolve document conflict versions. Text documents can also follow this migration process; that does not mean they offer the same multi-version selection panel.
If migration fails, the app may try to move migrated local content back to its original location. Check the actual error and whether documents open correctly; rollback handling does not make a failure irrelevant. Preserve files on both sides, record the timing and action sequence, and contact support if needed.
This article is current as of October 12, 2026; menus may vary across devices and versions.