Convert a FileMaker database to SQLite (Beta)

Move the tables of a .fp5, .fp7 or .fmp12 file into one SQLite database for SQL, Python or R.

Opens: FP3, FP5, FP7, FMP12
Saves: XLSX, CSV, SQLite, JSON

Convert

FileMaker files
Choose files… or drop them here
.fp3, .fp5, .fp7, .fmp12, .usr, .zip · up to 200 MB each, 50 files max
    Add more files

    One or more .fp3, .fp5, .fp7 or .fmp12 files (runtime solutions with their own extension work too), or a .zip of the solution folder. Old Mac files without an extension: put them in a .zip.

    Options
    More options

    Files from FileMaker Pro 3 to 6 do not record their character set. Automatic tells Mac and Windows files apart; pick another one if accented letters look wrong. Files from FileMaker 7 and later are always read correctly.

    Your files are deleted after processing.

    Moving a FileMaker solution to another system usually starts with getting its tables into a database that other software can read. This page reads .fp3, .fp5, .fp7 and .fmp12 files without FileMaker and writes all their tables into one SQLite file, ready for DB Browser for SQLite, Python, R, DBeaver or an import into PostgreSQL or MySQL.

    How to convert a FileMaker database to SQLite

    1. Upload the FileMaker file. For an older solution made of several .fp5 files (one per table), upload all of them or a .zip of the folder: they end up in one database.
    2. Check the preview of tables and records.
    3. Download the SQLite database (.sqlite).

    What is in the database

    • One SQLite table per FileMaker table, with one column per field (and per repetition of a repeating field). Table and column names are kept as they are in FileMaker, spaces and all, so quote them in SQL: SELECT "Unit Price" FROM "NW Line Items".
    • Number fields are declared NUMERIC: plain numbers are stored as numbers, while anything else that was typed into them stays text. All other fields are TEXT, with values exactly as FileMaker stored them.
    • Dates and times are text in the form FileMaker stored them (such as 1/4/1995). Convert them in SQL once you know the date order the file used.
    • _filemaker_fields lists, for every column, its source file, table, original field name, repetition, FileMaker data type and field kind, so nothing about the original types is lost.
    • Container fields hold the path of the extracted picture or file in the container ZIP.

    Things the database does not contain

    • Relationships, layouts, scripts, value lists and accounts: only the data is exported. Key fields (often named like _kp_ID and _kf_CustomerID) are ordinary columns, so you can join on them.
    • Unstored calculations and summary fields, which FileMaker computes on screen. They are listed on the Fields sheet of the Excel export.
    • SQLite allows 2,000 columns per table; a table with more columns keeps the rest in the CSV and JSON files, and the result says so.

    The upload is deleted as soon as the conversion finishes and the results are deleted after 30 minutes.

    More about what this tool reads and writes: FileMaker Database Rescue (.fp5, .fp7, .fmp12).