How the Agent Works
- Install the DataMeans Agent on the Magic application server
- Configure the connection to your Magic data directory
- Select the schemas and tables to extract
- The Agent extracts your data and uploads it securely for conversion
Magic (now uniPaaS/Magic xpa) is a rapid application development platform with an integrated database layer, using a metadata-driven architecture.
Why Agent Required
Magic applications typically run on servers with Btrieve/Pervasive backend databases that cannot be directly uploaded. The DataMeans Agent extracts data from your Magic environment.
What You Can Extract
- Magic xpa, uniPaaS, eDeveloper versions
- Underlying Btrieve/Pervasive data files
- Magic repository metadata
- Table structures and relationships
What You Get Out
DataMeans extracts your data into multiple modern formats:
| Output | Description |
|---|---|
csv/{TableName}.csv | One CSV file per table with all row data |
xlsx/{TableName}.xlsx | Excel workbook per table |
xls/{TableName}.xls | Legacy Excel format per table |
json/{TableName}.json | JSON array of records per table |
json/{TableName}.jsonl | Newline-delimited JSON (streaming-friendly) |
postgres.sql | PostgreSQL CREATE TABLE + INSERT statements |
schema/schema-graph.json | Relationship graph for visualization |
schema/er-model.json | ER model for diagram tools |
report.json | Structured extraction report |
report.md | Human-readable extraction summary |
How It Works
Agent availability: The DataMeans Agent is currently in development and not yet available for download. The steps below describe the planned workflow. To get notified when Magic support launches, reach out via our About page.
- Download and install the DataMeans Agent on the Magic application server
- Configure access to the Magic data directory
- Select schemas and tables to extract
- The Agent extracts data and uploads securely to DataMeans
- Review and download your converted data
Planned Support
- Btrieve/Pervasive file extraction
- Magic repository metadata parsing
- Table structure reconstruction
- Virtual field handling
Known Limitations
- Requires DataMeans Agent installation
- Magic-specific computed fields documented but not executed
- Some SQL backend databases may use direct SQL extraction instead
Overview
Documentation coming soon.
This article will contain vendor-neutral technical documentation about the data format used by Magic / uniPaaS applications, including:
- History and background
- File format specifications
- Data types and structures
- Version differences
- Technical references
To learn how to use this format with DataMeans, see the User Guide.
Not available for hosted uploads. This system is read over a direct database connection by the DataMeans Agent, which is still in development. Contact us to plan a migration.
Can I convert Magic / uniPaaS databases with DataMeans today?
Not yet. Magic / uniPaaS is not available for self-serve upload, and support is still in development. Get in touch and we'll tell you where it stands and help plan the migration.
What will DataMeans convert Magic / uniPaaS databases to?
Once Magic / uniPaaS is available, exports will match every other system we support: clean CSV, Excel, JSON & SQL, one file per table, with a structured report of exactly what was extracted.
Is my data secure?
Yes. Your files are encrypted in transit and at rest, and are automatically deleted once your conversion is complete. Your data is never sold, shared, or used for anything else.