Supported Formats
Applies to: Free · Pro · Enterprise
Last updated: 17-Jul-2025
Overview
Kazinex can import and export schedule data in multiple industry-standard formats. Files are parsed entirely in your browser — no upload is required for most formats.
Import Formats
Primavera P6 XER (.xer)
| Property | Detail |
|---|---|
| Extension | .xer |
| Source | Oracle Primavera P6 |
| Processing | 100% client-side |
| Max file size | 100 MB |
| Parse timeout | 60 seconds |
The XER format is a tab-delimited text file exported from Primavera P6. Kazinex parses all major tables:
- Projects, WBS hierarchy, Activities (87 fields), Relationships
- Calendars and calendar data (work weeks, exceptions, holidays)
- Resources and resource assignments
- Activity codes, code values, and code assignments
- User defined fields (UDF types and values)
- Cost accounts
Files with more than 1,000 activities are parsed in a Web Worker to keep the interface responsive. Smaller files are parsed on the main thread for faster results.
Primavera P6 XML / PMXML (.xml)
| Property | Detail |
|---|---|
| Extension | .xml |
| Source | Oracle Primavera P6 (XML export) |
| Processing | 100% client-side |
| Detection | Auto-detected by APIBusinessObjects tag |
Primavera P6 can export schedules in XML format using the APIBusinessObjects schema. Kazinex automatically detects PMXML files by inspecting the XML content and parses the same data model as XER.
Microsoft Project XML / MSPDI (.xml)
| Property | Detail |
|---|---|
| Extension | .xml |
| Source | Microsoft Project (Save As XML) |
| Processing | 100% client-side |
| Detection | XML files that are not PMXML |
Microsoft Project's XML format (MSPDI schema) is fully supported. Kazinex extracts tasks, summary/milestone flags, predecessors, calendars, resources, assignments, costs, float/slack, constraints, and percent complete. The data is normalised to Kazinex's internal format for full feature compatibility.
When you open a .xml file, Kazinex automatically determines whether it's a PMXML or MSPDI file.
Microsoft Project Binary (.mpp)
| Property | Detail |
|---|---|
| Extension | .mpp |
| Source | Microsoft Project (native binary format) |
| Processing | Server-assisted conversion |
| Requires | User consent before upload |
Binary .mpp files cannot be parsed in the browser. When you open an MPP file:
- Kazinex asks for your consent to upload the file for conversion.
- The file is sent to a secure conversion service (Java/MPXJ on Fly.io).
- The service converts it to MSPDI XML.
- The XML is returned and parsed client-side.
If the conversion service is unavailable, Kazinex prompts you to export the file as XML from Microsoft Project and open the XML version instead.
Kazinex Native (.kaz)
| Property | Detail |
|---|---|
| Extension | .kaz |
| Source | Kazinex |
| Processing | 100% client-side |
| Compression | ~90% smaller than XER/XML |
| Encryption | Optional AES encryption |
The Kazinex native format is a compact binary format optimised for fast loading. It supports:
- Compression — files are typically 90% smaller than the equivalent XER or XML
- AES encryption — optional password protection (prompted on open)
- Integrity checking — CRC32 checksums verify file integrity
- Round-trip fidelity — all schedule data is preserved exactly
Export Formats
Primavera P6 XER (.xer)
Exports a standards-compliant XER file using P6 version 20.0 format:
- Windows-style line endings (CR+LF)
- Full round-trip: projects, WBS, activities, relationships, calendars, resources, assignments
- Numeric ID remapping for consistency
- Compatible with Primavera P6 v20 and later
Primavera P6 XML / PMXML (.xml)
Exports using the APIBusinessObjects XML schema:
- ISO 8601 date format
- Compatible with Primavera P6 and MPXJ conversion tools
Microsoft Project XML / MSPDI (.xml)
Exports in MSPDI format that opens directly in Microsoft Project:
- ISO 8601 dates (no milliseconds)
- Durations in
PT#H#M#Sformat - P6 constraint types mapped to MSPDI constraint numbers
Note: The "MPP" export option in the menu produces MSPDI XML (
.xml), not a binary.mppfile. Microsoft Project opens this natively.
Kazinex Native (.kaz)
Exports in the compressed binary format with optional AES encryption.
CSV (Grid Data)
Exports the current Activities grid view as a CSV file:
- RFC 4180 compliant
- Includes only visible columns
- Proper field escaping
Note: CSV export captures the grid view only — it's not a full schedule interchange format. Use XER or MSPDI for complete schedule transfer.
CSV (Comparison Data)
Exports comparison results (activity changes, match types, impact scores) as a CSV file.
Format Comparison
| Feature | XER | PMXML | MSPDI | MPP | KAZ |
|---|---|---|---|---|---|
| Client-side parsing | ✅ | ✅ | ✅ | ❌ (server) | ✅ |
| Full schedule import | ✅ | ✅ | ✅ | ✅ | ✅ |
| Full schedule export | ✅ | ✅ | ✅ | ❌ | ✅ |
| Encryption support | — | — | — | — | ✅ |
| File size | Large | Large | Large | Medium | Small (~90% less) |
| Opens in P6 | ✅ | ✅ | — | — | — |
| Opens in MS Project | — | — | ✅ | ✅ | — |
Tips & Best Practices
- Use XER for Primavera P6 interchange — it's the most widely used P6 format with the highest fidelity.
- Use MSPDI for Microsoft Project users — the XML format is supported by all modern versions of MS Project.
- Use KAZ for archiving — the native format is compact, fast to load, and optionally encrypted.
- For MPP files, export as XML first — if the conversion service is slow or unavailable, simply save as XML from Microsoft Project.