Import Data with Advanced ETL Processor
Data import should be a repeatable workflow, not a heroic manual ritual performed whenever a file lands in a folder. Advanced ETL Processor imports Excel, JSON, XML, text, QVD, QVX, Parquet, and Clarion data into databases with validation, mapping, scheduling, and logs. Clarion TPS files are read directly, so you do not need ODBC just to use Clarion as the source. The file can still be dramatic. The process does not have to join in.
Imports belong inside the ETL workflow
Files rarely arrive clean, polite, and ready for loading. Columns move. Dates change formats. Empty values appear in places that make databases raise an eyebrow. Advanced ETL Processor keeps import rules next to transformation, validation, scheduling, and logging.
Start with the Advanced ETL Processor Enterprise overview, download the fully functional 30-day trial, use the video tutorials, or keep the WIKI open while you build.
Choose the source format you need to import
Excel
Load spreadsheets into databases with sheet, range, table, mapping, and validation rules kept inside one workflow.
Import Excel to AccessImport Excel to BDEImport Excel to DBFImport Excel to FirebirdImport Excel to Google SpreadsheetImport Excel to InterBaseImport Excel to MariaDBImport Excel to MySQLImport Excel to ODBCImport Excel to OleDbImport Excel to OracleImport Excel to PosgresqlImport Excel to SalesforceImport Excel to SQL Server CEImport Excel to SQL ServerImport Excel to SQLiteJSON
Import API responses, nested payloads, and service exports into database tables without turning every endpoint into a custom script.
Import JSON to BDE AutomaticallyImport JSON to DBF AutomaticallyImport JSON to Firebird AutomaticallyImport JSON to InterBase AutomaticallyImport JSON to Google Spreadsheet AutomaticallyImport JSON to MariaDb AutomaticallyImport JSON to MySQL AutomaticallyImport JSON to PostgreSQL AutomaticallyImport JSON to ODBC AutomaticallyImport JSON to OleDb AutomaticallyImport JSON to Oracle AutomaticallyImport JSON to Salesforce AutomaticallyImport JSON to SQL Server AutomaticallyImport JSON to SQL Server CE AutomaticallyImport JSON to Sqlite AutomaticallyImport JSON to Ms AccessParquet
Load analytical Parquet datasets into operational databases, reporting stores, and legacy systems that need table rows.
Import Parquet to DBF AutomaticallyImport Parquet to Firebird AutomaticallyImport Parquet to Google Spreadsheet AutomaticallyImport Parquet to Interbase AutomaticallyImport Parquet to MariaDB AutomaticallyImport Parquet to Ms Access AutomaticallyImport Parquet to MySQL AutomaticallyImport Parquet to Salesforce AutomaticallyImport Parquet to ODBC AutomaticallyImport Parquet to OleDb AutomaticallyImport Parquet to Oracle AutomaticallyImport Parquet to Postgresql AutomaticallyImport Parquet to SQL Server AutomaticallyImport Parquet to SQL Server CE AutomaticallyImport Parquet to Sqlite AutomaticallyQVD
Move Qlik QVD data into databases for reporting, migration, audit, and downstream ETL workflows.
Import QVD to AccessImport QVD to BDEImport QVD to DBFImport QVD to FirebirdImport QVD to Google SpreadsheetImport QVD to InterBaseImport QVD to MariaDBImport QVD to MySQLImport QVD to ODBCImport QVD to OleDbImport QVD to OracleImport QVD to PosgresqlImport QVD to SaleforceImport QVD to SQL Server CEImport QVD to SQL ServerImport QVD to SQLiteQVX
Import QVX connector output into supported targets when the next system needs rows rather than connector files.
Import QVX to BDEImport QVX to Google SpreadsheetImport QVX to AccessImport QVX to DBFImport QVX to FirebirdImport QVX to InterBaseImport QVX to MariaDBImport QVX to MySQLImport QVX to ODBCImport QVX to OleDbImport QVX to OracleImport QVX to PostgreSQLImport QVX to SalesforceImport QVX to SQL Server CEImport QVX to SQL ServerImport QVX to SQLiteText
Import CSV, delimited, fixed-width, and plain text files with encoding, delimiter, and field-mapping rules under control.
Import Text to AccessImport Text to BDEImport Text to DBFImport Text to FirebirdImport Text to Google SpreadsheetImport Text to InterBaseImport Text to MariaDBImport Text to MySQLImport Text to ODBCImport Text to OleDbImport Text to OracleImport Text to PostgreSQLImport Text to SalesforceImport Text to SQL Server CEImport Text to SQL ServerImport Text to SQLiteXML
Load structured XML into supported databases while preserving validation, transformation, and rejected-row handling.
Import XML to AccessImport XML to BDEImport XML to DBFImport XML to FirebirdImport XML to Google SpreadsheetImport XML to InterBaseImport XML to MariaDBImport XML to MySQLImport XML to ODBCImport XML to OleDbImport XML to OracleImport XML to PostgreSQLImport XML to SalesforceImport XML to SQL Server CEImport XML to SQL ServerImport XML to SQLiteClarion
Import Clarion TPS data directly into supported targets with no ODBC source connection, plus field mapping, validation, scheduling, and logs.
Import Clarion to AccessImport Clarion to BDEImport Clarion to DBFImport Clarion to FirebirdImport Clarion to Google SheetsImport Clarion to InterBaseImport Clarion to MariaDBImport Clarion to MySQLImport Clarion to ODBCImport Clarion to OLEDBImport Clarion to OracleImport Clarion to PostgreSQLImport Clarion to SalesforceImport Clarion to SQL ServerImport Clarion to SQL Server CEImport Clarion to SQLiteValidation matters before loading starts
For background, compare Microsoft Excel specifications and limits, RFC 8259 JSON specification, and W3C XML specification. The practical lesson is the same for every import: define the source layout, map fields, reject bad rows, and log the result.
Use automation when the import repeats
If an import happens once, a manual load may be enough. If it happens every day, week, or month, automate it. Advanced ETL Processor supports unlimited workflows, unlimited executions, and $0 row transfer fees. That is less exciting for cloud billing departments, which is rather the point.
Do not automate an import until the source layout, target table, key fields, and failure behaviour are agreed. Once those rules are clear, the boring part belongs to software.
Business usage examples
Operations lead
Turn repeated file imports into scheduled workflows with validation and clear logs.
Data team
Load Excel, JSON, XML, text, QVD, QVX, and Parquet data into supported databases.
Compliance owner
Keep original files, rejected rows, mappings, and run history visible enough for audit work.
FAQ
Can Advanced ETL Processor automate data imports?
Yes. It can import Excel, JSON, XML, text, QVD, QVX, and Parquet files into supported databases using scheduled workflows.
Does importing need scripting?
No scripting is required for routine import, validation, mapping, scheduling, and logging.
Can I test before buying?
Yes. Download the fully functional 30-day trial and build one small import first.
When should I not automate an import yet?
Do not automate it until the source layout, target table, key fields, and rejected-row rules are clear.
Can imports run on a schedule?
Yes. Import packages can run on a schedule, watch folders, process matching files, archive originals, and write logs for every run.
Can bad rows be rejected without stopping everything?
Yes. Use validation rules to reject bad rows, keep accepted rows moving, and record enough detail to fix the source file later.
Can imported data be transformed before loading?
Yes. You can clean values, convert data types, calculate fields, split columns, and apply lookup rules before writing to the target.
What should I define before the first import?
Define source layout, target table, key fields, write mode, date formats, rejected-row handling, archive location, and rerun rules.
Stop struggling with fragile ETL scripts. Start shipping reliable workflows.
Download the fully functional 30-day trial. Build your first automation in 10 minutes or less.
Direct link, no registration required.