Document Conversion Scenarios
Microsystems Conversion Services can help you with:
- Updating documents to your firm's styles
- Removing legacy numbering and table of contents
- Detaching documents from network-based templates
- Creating new document designs as a result of a merger
- Updating documents to a newer Word version
Scenario 1: Updating Documents to Your Firm's Styles
A lateral partner moves from another firm to yours, but his/her documents contain the original firm's branded style names.
- Problem: These styles are inappropriate for your firm, and changing them manually is unrealistic. Yet the partner will continue to 'borrow' content—and entire documents—as this work product is very familiar to him/her and his/her line of business.
- Microsystems Conversion Services: Through batch automation branded styles can be removed without impacting the visual and/or content fidelity of the document.
Scenario 2: Removing Legacy Numbering and Table of Contents
A lateral partner moves to your firm bringing a bevy of documents. These documents contain numbering and table of contents (TOC) artifacts that conflict with your firm automation for the same tasks.
- Problem: When generating a table of contents in your environment, artifacts from the partner's previous firm's TOC tool cause errors and/or unnecessary distraction and inconsistencies inside the document.
- Microsystems Conversion Services: Remove legacy TOC artifacts so that your automation generates without error, and the needless artifacts are removed.
Scenario 3: Detaching Documents from Network-Based Templates
A lateral partner moves from another firm to yours, but his/her documents open very slowly in your environment.
- Problem: Documents are attached to no-longer-accessible network-based templates.
- Microsystems Conversion Services: Detach the lawyer's former firm network-based templates, which often cause serious latency upon document open.
Scenario 4: Creating New Document Designs as a Result of a Merger
Your firm merges with another entity, and each source firm uses its own document and automation design.
- Problem: Documents have no consistency to one another, and it is not possible to represent the firm as a new cohesive entity.
- Microsystems Conversion Services: Update the latest version of reused work product with the newly created document design for the firm and merge that into the DMS using a batch process.
Scenario 5: Updating Documents to a Newer Word Version
Your firm upgraded to Microsoft Word 2010 or 2007 and is adopting the new .docx file format for all new work product, but your precedent or "top-drawer" documents remain in .doc.
- Problem: The .doc file format perpetuates because most new documents are created from previous documents. New work product continues to be developed without the benefit of the new features and functionality available in .docx and the firm is at risk for being perceived as behind the technology curve.
- Microsystems Conversion Services: In a batch process, bring precedent and top-drawer collections forward to the .docx file format. Using the DMS Utility the latest version of a document can be extracted from the DMS or file system, converted to .docx and then returned to the DMS.
