DBF, SDF, CSV, Access, SQL Server, MySQL, PostgreSQL, XML, and XLSX
all in one Windows application with field-level mapping, direct SQL integration, and Complex Routing.
Invaluable to any software developer, data analyst, service bureau, or end user working with multiple file protocols.
New in v4.0.0.1
Real-world data doesn't belong in one place. Orders need to reach the right regional database. Claims need to split by type. Exceptions need their own holding table for review.
Define a routing rule on any field in your data — order region, claim type, status code, whatever fits your business — and Universal File Converter reads your source file once, evaluates each record against your rules, and sends it straight to the correct destination. Every destination gets its own connection, its own SQL dialect, its own table, and its own field mapping.
No scripting. No XML wrangling. No SQL to write. Configure once, run with confidence.
Learn More About Complex Routing →Features
Built for telecom carriers, DBAs, and IT teams who move data between systems every day.
Map any input field to any output field. Auto-map by name, or assign manually. Handles truncation, padding, and 10-character DBF name limits automatically.
Build derived fields with inline expressions: arithmetic, string concatenation, conditionals with IIf(), and zero-padding for numeric results.
Filter records before conversion. Match on equals, not-equals, LIKE patterns, numeric comparisons, or EMPTY fields. Combine rules with AND / OR logic.
Create, drop, rename, and truncate tables visually across SQL Server, MySQL, and PostgreSQL. Manage indexes, set column constraints, and execute free-form SQL statements — no SSMS or external tool required.
Save, organize, and reuse conversion configurations as .cfg files. Create new configs, import from emigui, and edit field layouts in the built-in editor.
One pass, every destination. Route records from a single source to multiple SQL servers based on any field value — region, claim type, status code, or any business key. Each destination gets its own connection, SQL dialect, table, and field mapping. No scripting, no reruns.
Universal File Converter now supports three SQL engines: SQL Server, MySQL, and PostgreSQL. Read from or write to PostgreSQL tables with the same visual workflow used for every other format — including as a Complex Routing destination.
Run file-to-SQL and SQL-to-file conversions directly from the command line — no GUI required. Schedule conversions as Windows batch jobs or scripts against SQL Server, MySQL, or PostgreSQL. Ideal for service bureaus, developers, and automated data pipelines.
Import fixed-width record layouts directly from COBOL copybooks — no manual field-position counting. Parse and route X12 EDI transactions (835 Remittance Advice and 837 Claims) by segment type into SQL Server, MySQL, or PostgreSQL using the same routing engine that powers every other data source.
Compatibility
Convert between any combination of these nine formats, with EDI X12 and COBOL Copybook as additional input sources.
| Format | Extension | As Input | As Output | Requirements |
|---|---|---|---|---|
| DBF (dBase / FoxPro) | .dbf | ✓ Yes | ✓ Yes | None |
| SDF (Fixed-Width) | .txt / any | ✓ Yes | ✓ Yes | Field layout in .cfg file |
| Delimited (CSV) | .csv / .txt | ✓ Yes | ✓ Yes | None |
| Microsoft Access | .mdb / .accdb | ✓ Yes | ✓ Yes | Access Database Engine |
| SQL Server / Azure SQL | n/a | ✓ Yes | ✓ Yes | ODBC Driver 17+ |
| MySQL | n/a | ✓ Yes | ✓ Yes | MySQL ODBC Driver |
| PostgreSQL NEW v4 | n/a | ✓ Yes | ✓ Yes | PostgreSQL ODBC Driver |
| XML | .xml | ✓ Yes | ✓ Yes | None |
| Excel XLSX | .xlsx | ✓ Yes | ✓ Yes | None |
| EDI X12 (835 / 837) NEW v4 | .edi / .txt | ✓ Yes | via SQL routing | Starter templates included |
| COBOL Copybook NEW v4 | .cpy / .cbl | ✓ Yes | layout import | None |
How It Works
From raw data file to converted output in minutes.
Open or create a .cfg file that defines your input field layout and output structure.
Browse for your input file or connect to a SQL Server / MySQL table.
Use the Field Mapper to link input fields to output columns. Auto-Map handles matching names instantly.
Click Convert. The status bar shows Written / Skipped / Total counts in real time.
See It In Action
Load a config, select formats, map your fields, and click Convert — results in seconds.
What's New
Major new capabilities in the current release.
FAQ
Quick answers to the questions we hear most often.
No. You need the free Microsoft Access Database Engine 2016 Redistributable, available from Microsoft.com. The full Microsoft Office or Access suite is not required.
Yes. SQL Server mode connects to Azure SQL, on-premises SQL Server (2012 and later), and SQL Server Express using ODBC Driver 17 or later.
We offer a 30-day money-back guarantee on all direct purchases..
Yes. SQL Server connections support both Windows Authentication and SQL Server (username / password) credentials. MySQL connections require SQL credentials.
Universal File Converter runs on Windows 10 and Windows 11 (64-bit). It is a native Windows desktop application — no browser or cloud service required.
Yes. Every configuration — field layouts, mapping, skip rules, and output settings — is saved as a .cfg file. The Config Manager lets you load, create, edit, and organize configs in one place.
The engine is optimized for high-volume batch work. Conversions of 100,000+ records per pass are typical in production environments. Performance depends on disk I/O, SQL server throughput, and available RAM.
Complex Routing reads your source file once, evaluates each record against your routing rules, and sends it to the correct SQL destination. Every destination gets its own connection, SQL dialect, table, and field mapping — no reruns, no separate config files.
Yes. v4.0.0.1 adds PostgreSQL as a full third SQL engine. You can read from or write to PostgreSQL tables using the same visual workflow as SQL Server and MySQL — including browsing tables, running conversions, and using PostgreSQL as a Complex Routing destination. Requires the PostgreSQL ODBC driver installed on your machine.
EDI X12: Universal File Converter parses X12 EDI files and routes each segment type to its own SQL destination table. Starter templates are included for 835 (Remittance Advice) and 837 (Health Care Claim). Segment and element delimiters are auto-detected from the ISA envelope — no manual configuration. Templates are standard .cfg files you can extend for additional segments.
COBOL Copybook: Point the app at a .cpy, .cbl, or .cob file and it builds the field layout automatically from PIC clauses — position, length, and type computed without manual counting. Handles nested groups, OCCURS N TIMES, and REDEFINES. COMP/COMP-3/binary fields are safely detected and excluded rather than misread.
Yes. v4.0.0.1 adds full Headless CLI SQL support — file-to-SQL and SQL-to-file conversions can be run directly from the command line using batch switches, with no GUI required. This makes it straightforward to schedule conversions as Windows batch jobs or scripts. SQL-to-SQL is not supported in headless mode; all other format combinations work.
About
Telconsult, Inc. is a telecom software company with over four decades of experience in carrier access billing, CLEC operations, long-distance carrier services, and international interconnect. Universal File Converter is built on real production data requirements — not theoretical edge cases.
Pricing
Full 9-format conversion engine with Complex Routing, PostgreSQL, EDI X12, and COBOL Copybook Import.
Version 4 available now — direct purchase at nextgencarrier.net. Windows 10 and Windows 11.
View Plans & Pricing →Questions? Email [email protected]