Before moving a manuscript, preserve a separate research record that connects important claims with their sources and review status. Test how the destination tool handles notes and references using a representative section. After the transfer, confirm the relationships in the editable project and the intended output rather than assuming that visible text carries all of its supporting evidence.
Identify the evidence that lives outside the prose
List the places where the project stores research information. Sources may appear in footnotes, endnotes, comments, a reference manager, or an independent research document. Some records are intended for readers, while others explain an internal editorial decision. Identify both types before moving files so a transfer that preserves the main text does not quietly discard the reasoning behind it.
Pay attention to unresolved questions and qualifications. A comment may explain that a number still needs verification or that a paragraph applies only under certain conditions. Losing that comment can make provisional prose appear accepted. Record the status in a maintained issue list before transfer rather than relying on a hidden annotation to remain attached through every tool conversion.
Use stable identifiers for claims and sources
Give important source records identifiers that remain useful when chapters or page numbers change. Connect the relevant claim or section to the source, its date, and the reason it supports the text. The record should explain the relationship, not simply store a long list of links. A later editor needs to know which statement the source was used to verify and what limits were recognized.
Keep quoted material distinguishable from the author’s notes and paraphrases in the research workspace. During a transfer, text can lose formatting that originally signaled those differences. Preserve the distinction explicitly so a drafting note does not become unmarked book prose. Review any publication treatment separately; organizing a source record does not by itself resolve every question about quoting or reusing material.

Test a representative section before moving everything
Choose a section containing the structures you depend on, such as a footnote, a cross-reference, a source-linked table, and an unresolved editorial comment. Import it into the destination workflow and inspect what survives. Check the content of notes as well as their numbering and association with the text. A familiar-looking superscript is not proof that its intended note transferred correctly.
Record the cleanup needed and decide where the authoritative research record will live after the move. If the tool cannot preserve an internal note type, provide a deliberate replacement process before transferring the full manuscript. Avoid discovering late in production that hundreds of claim notes have become detached and can only be reconstructed by comparing several old files manually.
Reconcile the transferred text with its support
After migration, review the important claim-to-source relationships in the accepted working project. Confirm that the source still supports the wording actually present. An import cleanup or AI-assisted rewrite can change a cautious statement into a stronger claim even when the original reference remains visible. Evidence review needs to follow meaning, not only the continued existence of a citation marker.
Check unresolved items separately from completed verification. Make sure open questions did not disappear because the destination tool lacks the previous status labels. Preserve the owner and next action for each material issue. If a source is no longer accessible, record that limitation and determine what additional verification is needed instead of treating the old link as self-sufficient proof indefinitely.

Preserve reader notes and internal records in the right places
Review the intended output to ensure that reader-facing references appear where they belong and remain usable in the chosen format. Follow the current preparation guidance for the actual book format. Also inspect for internal comments, temporary research text, or unresolved instructions that should not appear in the publication. The accepted output and internal evidence record serve different audiences and need separate checks.
Archive the maintained research record with the editable manuscript and the reviewed export version. Record the transfer method and any deliberate limitations so the next editor can understand what changed. This gives future revisions a reliable starting point. A successful migration should preserve not only readable paragraphs but also the ability to explain, verify, and responsibly revise the claims those paragraphs contain.
Frequently asked questions
Clear answers for this publishing decision.
Does preserving all visible footnotes prove the research record survived?
No. Internal comments, source notes, and unresolved verification tasks may exist elsewhere. Check the full evidence workflow and confirm that each important note still relates to the intended claim.
Should internal verification notes appear in the published book?
Only material intentionally prepared for readers should appear in the output. Keep internal decisions and open issues in the maintained project record, and inspect the export for accidental inclusion.
What if the new tool cannot import a note type?
Create a deliberate replacement record and test how editors will use it before moving the full manuscript. Do not rely on an unsupported transfer to preserve information essential to later verification.
How do I get from an idea and a brief to an editable manuscript I can finish?
Write the brief first, generate a structure you can edit, then draft and revise the manuscript in reviewable sections so one change never overwrites work you already approved.
Start a book project from a brief