Universal File Conversion Tool

Features

Core Capabilities

• 🗂️

  Field-Level Mapping

  Map any input field to any output field by name or position. Auto-Map assigns fields automatically where names match. Manual overrides handle renamed, reordered, or renamed columns. The mapper enforces 10-character DBF field name limits automatically and handles truncation and padding for fixed-width SDF output.

• 🧮

  CALC Expressions

  Derived output fields are built with inline CALC expressions supporting arithmetic operators, string concatenation, conditional logic via IIf(), zero-padding for numeric fields, and substring operations. CALC fields are computed at conversion time with no preprocessing required.

• ⏭️

  Skip Rules

  Records can be filtered before conversion using one or more skip rules applied to any input field. Supported match operators include equals, not-equals, LIKE pattern matching, numeric comparisons (<, >, <=, >=), and EMPTY field detection. Multiple rules are combined with AND or OR logic.

• 🗄️

  SQL Table Manager

  A full SQL table management interface is built directly into the application. Users can create, drop, rename, and truncate tables across SQL Server, MySQL, and PostgreSQL; manage column indexes; set column constraints including UNIQUE; and execute free-form SQL statements through the built-in Run SQL executor — without requiring SQL Server Management Studio or any other external tool.

• 🔀

  Complex Routing: One Pass, Every Destination NEW v4

  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. Traditionally, that means writing and maintaining a separate conversion for every destination — Complex Routing replaces all of it with a single visual workflow.

  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, so a single conversion run can write orders from the East region into a SQL Server table, West region orders into MySQL, and anything unmatched into a PostgreSQL catch-all — no manual reruns, no juggling separate config files by hand.

  It's built entirely around a visual, point-and-click editor: pick your routing field, define your match values, browse to each destination's configuration, and you're done. No scripting, no XML wrangling, no SQL to write. Whether you're distributing order data across regional systems, splitting insurance claims by transaction type, or routing CDR records by carrier, Complex Routing turns what used to be a multi-step, multi-tool process into a single conversion you configure once and run with confidence.

• 🏥

  EDI X12 & COBOL Copybook Import NEW v4

  COBOL Copybook Import: Point the application at a .cpy, .cbl, or .cob file and it parses PIC clauses directly into a usable field layout — position, length, and type computed automatically. Handles nested group hierarchies, OCCURS N TIMES (expanded into indexed fields), and REDEFINES (correctly resolved to the original field's position). COMP/COMP-3/binary fields are detected and safely excluded rather than misread.

  X12 EDI Support: The app auto-detects element, sub-element, and segment delimiters from the ISA envelope — no manual configuration required. A two-step workflow converts the EDI file into a structured intermediate format, then routes each segment type to its own destination SQL table using the standard multi-destination routing engine. Starter templates for 835 (Remittance Advice) and 837 (Health Care Claim) are included.

  Full technical documentation →

• 📋

  Config Manager

  Conversion configurations are stored as .cfg files and managed through the built-in Config Manager. Each config captures input and output format selections, field layouts, field mappings, skip rules, CALC expressions, and output options. Configs can be created from scratch, imported from emigui, edited in the built-in configuration editor, and reused across jobs without re-entry.

• ⌨️

  Headless CLI SQL Support NEW v4

  File-to-SQL and SQL-to-file conversions are now fully supported in headless (no-GUI) batch mode via command-line switches. Any saved .cfg file that defines a file-to-SQL or SQL-to-file conversion can be executed directly from a Windows batch script or Task Scheduler job — making it straightforward to automate recurring data loads, scheduled exports, and nightly ETL runs against SQL Server, MySQL, or PostgreSQL without any manual interaction. SQL-to-SQL is not supported in headless mode; all other format combinations are.

Supported Formats

Format Conversion Matrix — Version 4

Any format in the table below may serve as either input or output. Conversions between any two formats are supported in a single pass — no intermediate file required. EDI X12 and COBOL Copybook are additional input sources that route to SQL destinations.

* Microsoft Access Database Engine 2016 Redistributable is a free download from Microsoft and does not require Microsoft Office or Access to be installed.

Use Cases

Who Uses Universal File Conversion Tool

System Requirements

Technical Requirements

Licensing & Availability

How to Get Universal File Conversion Tool

For licensing questions or volume inquiries, contact [email protected].