Convert FP7 to XLS

A recipient may require an Excel workbook for tabular editing, reporting, or import into software that cannot read a FileMaker database. Converting the records to .xls provides compatibility with older Excel installations and legacy business systems, but it does not convert the database structure.

What the FP7 format is

.fp7 is the FileMaker Pro database format used by FileMaker Pro 7 through FileMaker Pro 11. An FP7 file can contain tables, fields, relationships, layouts, scripts, calculations, value lists, container fields, indexes, and account permissions. Older business databases, contact systems, inventories, research records, and archives commonly use this format.

FP7 is not a spreadsheet. Data can be distributed across related tables, while a layout can display calculated, summary, or related values that are not ordinary stored columns. FileMaker Pro is normally required to interpret the database correctly before export.

What the XLS format is

.xls is Microsoft Excel's binary workbook format, associated mainly with Excel 97–2003 and older software integrations. It stores rows and columns, formulas, basic formatting, and charts in a form accepted by applications that do not support newer .xlsx workbooks.

An XLS worksheet is limited to 65,536 rows and 256 columns. XLS cannot preserve FileMaker relationships, layouts, scripts, privileges, validation rules, indexes, portal behavior, or the database schema.

How to convert FP7 to XLS

1. Back up the original. Work on a copy of database.fp7. Obtain the required account credentials if the file is protected.
2. Open the copy in FileMaker Pro. FileMaker Pro 11 can open FP7 files without changing them. FileMaker Pro 12 and later can generally convert an FP7 file to the newer FileMaker format when it opens it; keep the original because that conversion creates a new file and may not be reversible. Use a compatible FileMaker installation and confirm that scripts, calculations, and relationships load correctly.
3. Select the required records. Open the appropriate table occurrence or layout, perform a find if only a subset is needed, and verify the found-record count. The active layout context affects related and calculated fields.
4. Choose File → Export Records.
5. In the export dialog, select the fields and order required for the spreadsheet. Check calculated, summary, and related fields carefully; their exported values depend on the current record, context, and calculation state.
6. If the FileMaker version offers an Excel export option, choose it and create an intermediate .xlsx file. FileMaker versions that support Excel export commonly produce newer Excel workbooks rather than the older .xls format.
7. Open the intermediate workbook in Microsoft Excel or LibreOffice Calc. In Excel, choose File → Save As, select Excel 97-2003 Workbook (*.xls), and accept the format warning. In Calc, choose File → Save As, select Excel 97-2003 (.xls), and retain the requested format when prompted.
8. Reopen the resulting .xls file and check row and column counts, headers, dates, numeric values, formulas, non-ASCII characters, blank values, and identifier fields such as ZIP codes or account numbers.

If direct Excel export is unavailable, use File → Export Records to create a UTF-8 CSV file. Open the CSV through Excel or Calc's import process, select the correct delimiter and UTF-8 encoding, set identifiers to Text to preserve leading zeroes, then save as .xls. CSV preserves tabular values but does not preserve FileMaker formatting, formulas, relationships, or container data.

Online services are generally not a direct solution for FP7 because many do not parse the proprietary FileMaker structure. For a non-confidential .xlsx file that FileMaker has already produced, services such as Zamzar or CloudConvert may offer .xlsx-to-.xls conversion when that format pair is listed on their current sites. Do not upload personal, regulated, or commercially sensitive database records without authorization, and verify the converted workbook locally.

Quality and compatibility limits

• The export contains selected fields from selected records, not the original FileMaker application. Preserve the FP7 file separately if the database logic or audit history is needed.
• Related fields, calculations, summary fields, and portal data may depend on layout context or related-record state. Test representative records before exporting the full dataset.
• Container fields can contain images, documents, audio, or other files. Excel export may not preserve them as usable embedded content; export container contents separately when they must be retained.
• Repeating fields, multi-value text, portal rows, and summaries do not always map to one flat XLS row. Decide whether to flatten, split into separate exports, or retain the source database.
• Datasets exceeding 65,536 rows or 256 columns require multiple files or worksheets, a newer .xlsx workbook, or another data format. Saving modern formulas, formatting, or character data as XLS can cause compatibility warnings or feature loss.