Test Note Conversion Before Moving a Manuscript

Before moving a manuscript between tools, test several kinds of notes in a small copy. Confirm that each note stays attached to the correct passage, preserves its contents, and can still be edited. Compare the returned file as well as the initial import before trusting a full transfer.

Build a sample that contains difficult notes

A chapter with one short footnote is an inadequate test for a heavily annotated book. Include notes with multiple paragraphs, source details, cross-references, and punctuation that matters. Add two notes close together and one attached to a sentence that you will move during the test.

Use a copy of real manuscript material with appropriate privacy precautions. Preserve an untouched reference file. The purpose is to reveal conversion behavior before it reaches the working manuscript, so write down what each sample note is meant to explain and where its marker belongs.

Distinguish the marker from the note’s identity

A displayed number can change when a passage moves. That change may be correct. What matters is whether the associated note remains connected to the intended statement. Record a short identifying phrase from each note so you can recognize it even after the tool renumbers the sequence.

Check the surrounding sentence, not merely the presence of the number. If a conversion moves a marker to the end of a paragraph, a source that originally supported one claim may appear to support several. The text may look tidy while its evidentiary meaning has changed.

Check the imported editing behavior

Open each note in the receiving application and make a small revision. Determine whether the application recognizes an editable note or merely displays text that resembles one. A pasted note list at the end of a chapter may preserve words while losing the relationship needed for later editing.

Move the sampled sentence and insert a new note before it. Then check numbering, attachment, and contents again. This is a practical stress test of ordinary revision, not an attempt to evaluate every feature of the tool. Record failures with the exact source and destination file versions.

Inspect the return path separately

Export the sample back to the format used for your production handoff. An application may import notes successfully but export them differently. Open that returned file independently and compare it with the reference, including note order, paragraph breaks, and any symbols or source links that matter to the manuscript.

If the workflow deliberately converts footnotes into endnotes, evaluate that result on its own terms. Confirm that readers can identify the relevant note and return to the passage. Do not call the conversion successful solely because the text is present somewhere in the document.

Resolve exceptions before a full migration

Classify each problem by its effect. A changed display style may be repairable through a document setting. A detached marker or missing paragraph requires content repair. A note converted into ordinary text may require rebuilding the relationship or choosing a different transfer method.

Estimate the repair effort from the number and type of affected notes, not just the total document length. Preserve a list of unresolved cases. If the small sample already loses meaningful connections, transferring the entire manuscript first will make the diagnosis harder and increase the amount of material that needs reconciliation.

Protect the final publication handoff

After the full transfer, check all notes affected by movement or conversion and sample the remainder systematically. Keep the reference and the transfer report until the publication files have passed their own review. The editing tool's successful round trip does not establish that every publication format will present notes correctly.

KDP provides separate formatting guidance for different book formats. Use the appropriate output checks after the manuscript leaves the writing environment. Preserve a clear boundary between a verified editing workflow and a verified reader-facing file, while keeping enough information to trace a failed note back to its source.