Before converting a single file, the first step in any legacy document migration is a thorough audit. Moving thousands of .lwp files to .docx isn't just a copy-paste job; it's a careful process of preserving information. Skipping this analysis phase is a common mistake that leads to lost data, broken documents, and project delays. The goal is to understand the scope and complexity of your document library, allowing you to categorise files and choose the right migration strategy for each set.

Your legacy archive likely contains more than one type of file, even if they all seem related to Lotus. The two primary formats you'll encounter are Lotus Word Pro (.lwp) and its predecessor, Ami Pro (.sam). While Word Pro was designed to be backwards-compatible with Ami Pro, their internal structures are different. Correctly identifying each file type is crucial because the tools and techniques for conversion can vary.

Beyond the file extension, you need to look inside the documents for embedded content. Many older documents rely on Object Linking and Embedding (OLE) to include content from other programs, such as a spreadsheet from Lotus 1-2-3 or a chart. These embedded objects are a major conversion risk. The links are often path-dependent and fragile, meaning they will almost certainly break during migration, leading to missing or corrupted content in the final .docx file.

Once you've identified file types and the presence of OLE objects, the next step is to audit for structural complexity. Features that were common in desktop publishing-oriented software like Word Pro don't always have a direct equivalent in modern word processors. Look for:

• Frames: Word Pro used frames extensively for layout, allowing text and images to be placed anywhere on the page. Microsoft Word handles this differently, primarily through text boxes and tables, so conversions are often imperfect.
• Complex Tables: Nested tables or tables used for page layout rather than data presentation can be difficult to convert accurately.
• Custom Scripts: Some documents may contain macros or scripts written in LotusScript. These will not function in a .docx environment and must be identified for potential manual recreation.

Equally important is the document's metadata, which includes details like author, creation date, modification history, and keywords. This information can be critical for compliance, legal, and archival purposes. Standard conversion tools often discard this data. A proper migration plan must include a strategy for extracting and mapping this metadata to the corresponding fields in the new .docx files.

With your audit complete, you can now categorise all documents based on their conversion risk. This framework will determine which migration pathway—automated, manual, or a hybrid—is most appropriate. A simple scoring system can help formalise this process.

This initial analysis is the foundation of a successful migration. By understanding exactly what you're working with, you can prevent data loss, manage project timelines effectively, and ensure the integrity of your document archive for years to come.