Manually Migrating Custom Letter Templates After a QuickBooks Enterprise Downgrade

Custom letter templates do not carry over during an Enterprise downgrade; here is how to export them from the original file and import them into the downgraded file.

When a QuickBooks Enterprise company file is downgraded to Pro or Premier, the conversion process transfers transactions, lists, and reports — but custom letter templates are left behind. Our engineers field regular calls about this gap. The templates live in a separate layer of the company file that the downgrade tooling does not touch, so any personalized customer correspondence, collection notices, or welcome letters you built in Enterprise must be moved manually. This page walks through that process.

Preconditions

Before starting, make sure you have:

• Both files accessible. You need the original Enterprise file (or a working backup of it) and the downgraded file, both on the same machine or reachable over your network.
• The same QuickBooks version installed. Open both files in the target edition (Pro or Premier) that the downgrade produced. Do not attempt the export from inside Enterprise if the downgraded file requires a different version year.
• A verified backup of the downgraded file before you import anything. If an import goes wrong, you want a clean restore point.
• Single-user mode active in the file you are importing into. Switch via File → Switch to Single-user Mode.

Exporting Templates from the Original File

1. Open the original Enterprise company file (or restore the backup you made before the downgrade began).
2. From the top menu, go to Lists → Templates.
3. In the Templates list, select the first custom letter template you want to migrate.
4. Click the Templates button at the bottom of the window (or right-click the selected template) and choose Export.
5. In the export dialog, verify that the template type and name are correct, then save the file to a known folder on your local drive. QuickBooks exports letter templates as .des (design) files.
6. Repeat for each additional template. You can export them one at a time; there is no bulk-export option for letter templates in most QuickBooks Desktop versions.

If the Export option is greyed out, confirm that the template is a custom one you created or modified. Built-in default templates cannot be exported and do not need to be — they already exist in the target file.

Importing Templates into the Downgraded File

1. Open the downgraded Pro or Premier company file.
2. Confirm you are in single-user mode.
3. Go to Lists → Templates.
4. Click the Templates button at the bottom and choose Import.
5. Navigate to the folder where you saved the exported .des files.
6. Select the first file and click Open.
7. QuickBooks displays a preview of the template. Review the name and type, then click OK to complete the import.
8. Repeat for each remaining template.

Verifying the Import Worked

Open Lists → Templates in the downgraded file and confirm each imported template appears with the correct name and type. To functionally test a template:

1. Open a customer or vendor record.
2. Go to Word → Create Letter (or the equivalent menu for your version).
3. Select the imported template from the available templates list.
4. Confirm the letter generates with the expected formatting, merge fields, and logo.

If merge fields populate correctly and the layout matches what you had in Enterprise, the migration succeeded.

When This Might Not Be Enough

Template migration is generally straightforward, but a few situations can complicate it:

• Version-year mismatches. If the Enterprise file was from a different year than the downgraded file, template formatting may shift slightly. Fonts, margins, and embedded images occasionally need manual adjustment after import.
• Linked attachments or logos. If a template references an external image file (such as a company logo stored on a specific drive path), that path must resolve on the machine where the downgraded file is opened. Broken image links produce blank space rather than error messages.
• Damaged templates. If the original Enterprise file has structural damage, the export itself may fail. In that case, the underlying file may need repair before templates can be extracted.

If the export consistently fails across all templates, the source file likely has damage in the template layer. That points to a broader company-file issue rather than a template-specific one.