Skip to content
Kairos OneBook a demo
Menu
Advanced · 3 min read

Import, export, and validate P6 XER files

Exchange native schedule data without losing lineage, overwriting global data blindly, or mistaking a successful import for parity.

Working definition

XER is Oracle’s proprietary P6 exchange format. It can carry project data and references to calendars, codes, resources, relationships, and other enterprise objects. Import success means P6 accepted the file; it does not prove that the target database calculated identical dates, preserved every authored field, or avoided changes to shared enterprise data.

Version scope

Desktop P6 Professional workflow. Menu labels are aligned with Oracle’s current Version 26 help; older 24.x deployments may show minor wording or privilege differences.

Key takeaways

  • Preserve the raw XER, checksum, source, version, and import/export options.
  • Review mappings and global-data conflicts before committing the import.
  • Validate counts, fields, dates, calculation settings, and a post-import export—not just the success message.
01

Treat exchange as a controlled transformation

Record source environment, P6 version, project ID, export time, file hash, selected projects, and export options. On import, preserve the raw file, document mappings and update choices, and use a sandbox or controlled database when global data conflicts are possible.

02

Validate after import and after scheduling

Compare activity and relationship counts, calendars, codes, constraints, actuals, durations, resources, baselines, and key dates. Then schedule under documented options and compare the exported result with the source. Differences may arise from version, database configuration, calendars, global objects, or calculation settings.

Exchange an XER with reproducible lineage

Use a nonproduction or controlled target first when the source database is unfamiliar.

Menu path: File > Export > Primavera PM (XER); File > Import > Primavera PM (XER)

Before you start

  • Raw source XER
  • Recorded checksum and source
  • Target-database backup or sandbox
  • Mapping and global-data policy

  1. Inventory the source

    Record filename, hash, size, source environment, P6 version, export timestamp, project IDs, and expected data date.

    Verify: The file can be uniquely identified later.

  2. Export deliberately

    Choose File > Export, Primavera PM (XER), version, Project, selected projects, and controlled destination.

    Verify: The completion message and resulting file match the intended project set.

  3. Preview the target

    Before import, confirm environment, EPS destination, existing Project IDs, privileges, calendars, codes, resources, and backup state.

    Verify: Potential collisions and shared-data effects are understood.

  4. Review import actions

    Choose File > Import and inspect project, layout, and data mappings plus create/update/keep decisions.

    Verify: No existing project or global object will be overwritten unintentionally.

  5. Validate before scheduling

    Compare object counts and authored fields with the source record.

    Verify: Activities, relationships, calendars, codes, actuals, durations, constraints, and required resources reconcile.

  6. Schedule and round-trip

    Run the documented calculation, save the log, export a fresh XER, and compare critical fields and key dates.

    Verify: Any difference is explained, accepted, or treated as a failed exchange.

    Field-ready control

    XER exchange control

    • Raw source retained
    • Checksum and lineage recorded
    • Correct target environment
    • Backup or sandbox available
    • Mappings reviewed
    • Global data protected
    • Counts and fields reconciled
    • Scheduling options recorded
    • Round-trip export compared
    • Temporary or test records cleaned up

    Common questions

    Is an XER a complete database backup?

    No. It is a project and data exchange file, and its contents depend on export choices and referenced objects. Database backup, security, job-service, document, audit, and environment configuration require separate controls.

    Sources and scope

    Follow the reference trail.

    This guide is original educational commentary. Kairos reference records identify the source organizations, editions and scope behind this guidance. The original publishers retain their publications and rights.

    Export projects to an XER fileOracle · checked 2026-08-01Import projects in XER formatOracle · checked 2026-08-01XEROracle · checked 2026-08-01Primavera P6 Professional User Guide, Version 26Oracle · checked 2026-08-01Schedule Assessment Guide: Best Practices for Project SchedulesU.S. Government Accountability Office · checked 2026-08-01