Convert WDB to CSV

A spreadsheet, database, reporting system, or import service may require records from an old Microsoft Works database in CSV format. Conversion also provides a more accessible copy for editing, sharing, and archiving, but it can discard database structure and formatting.

What the WDB format is

WDB commonly identifies a Microsoft Works Database file created by Microsoft Works, a discontinued office suite for Windows. A Works database can contain fields, records, formatted values, calculated fields, and memo-style text; files may come from Works versions 2.x through 9.x.

The .wdb extension is not unique to Microsoft Works. Confirm the program that created the file before choosing a converter. A WDB file produced by another application may require that application’s own export function and may not open in Microsoft Works.

What the CSV format is

CSV is a plain-text representation of tabular data. Each record normally occupies one line, while commas separate fields; some programs use semicolons, tabs, or another delimiter instead. Fields containing commas, quotation marks, or line breaks must be quoted according to the CSV rules.

Excel, LibreOffice Calc, Google Sheets, database systems, programming languages, and many import services can read CSV. It does not preserve Works relationships, indexes, formulas, field types, page layout, or most formatting, and a CSV file normally represents one table rather than an entire database.

How to convert a Microsoft Works database

Use Microsoft Works for the most complete export

1. Make a backup of the original .wdb file and work on the copy.
2. Open the copy in the Microsoft Works version that created it, or in a compatible licensed Works installation.
3. Inspect the records and fields, and remove data that should not be exported.
4. Use File → Save As or File → Export. The exact command and available formats depend on the Works version.
5. Choose a CSV, delimited-text, or text format if offered. For text export, select a comma delimiter when the program provides delimiter settings. If the export does not include field names, add a header row later in a spreadsheet editor.
6. Open the exported text file in LibreOffice Calc or Excel through its import dialog. Select the correct delimiter, text encoding, quote character, and column types before loading the data.
7. Check the imported table, then save it as database.csv using the required encoding and delimiter.

Microsoft Works is discontinued and is not supplied by current Microsoft 365 or Windows installations. If a licensed copy is available, an isolated older Windows computer or virtual machine may be needed. Do not use unverified “abandonware” downloads, which may be modified or unlawful.

Use an online converter for nonconfidential files

Reputable conversion services such as Zamzar and Convertio may list WDB-to-CSV conversion, but support can vary by the specific Works version and by changes to the service. Upload a duplicate, confirm that the service identifies it as a Microsoft Works Database, and test the result with a small nonconfidential file before processing the full set.

Do not upload personal, financial, medical, legal, or business records to a third-party service unless its handling, retention, and deletion terms meet your requirements. If the service rejects the file, creates an empty CSV, or loses fields, use Microsoft Works or the original application instead. LibreOffice Calc and Excel are useful for inspecting and resaving an exported text file, but neither provides reliable direct support for every Microsoft Works Database variant.

Check the converted data

• Select UTF-8 when the exporter or spreadsheet import dialog supports it. Older Works files may use a Windows code page, causing accented or non-Latin characters to change.
• Set identifier columns such as postal codes, telephone numbers, account numbers, and product codes to text before importing so leading zeroes are retained.
• Verify dates, decimal separators, Boolean values, empty fields, and numeric precision; CSV stores values as text and does not carry their original data types.
• Check commas, quotation marks, and embedded line breaks. A valid CSV can contain these characters inside quoted fields, but the receiving program must parse them correctly.
• Confirm that every record has the expected number of columns and that the first row contains the intended field names.
• Review calculated fields and linked data separately. An export may contain displayed results but not the formulas, relationships, or source tables needed to reproduce them.
• Keep the original .wdb file and the exported copy. CSV conversion is usually lossy and cannot reconstruct the Works database structure.