Import a Read-Only Project Schedule

Background

Importing a Read-Only schedule preserves your master schedule logic by keeping the imported data grayed out. Acting as a foundation for field execution, this option protects the master schedule while unlocking a separate editable Lookahead tab where field teams can build out granular day-to-day plans.

Things to Consider

  • Required User Permissions:

    • 'Standard' level permissions or higher on the project's Scheduling tool.

  • Additional Information:

    • Procore supports .ppx (Phoenix), .mpp (Microsoft Project), and .xer (Primavera P6).

    • New Beta Formats: As of July 21, 2026, native file imports are now supported in Open Beta for Asta Powerproject (.pp) and MS Project XML (.xml/ MSPDI). Note that Asta .pp and MS Project. xml` support import only; exports are not available. Go to Manage Features With Procore Explore to join the beta.

    • Smartsheet users must export to XML first (file-based import, not direct API).

    • When importing, the project calendar is carried over directly from the native source file.

    • Note for Oracle Primavera Cloud (OPC) Users: For .xer files generated via OPC that lack unique GUIDs, Procore now utilizes a fallback identification strategy mapping Activity IDs and System-generated Object IDs. This ensures lookaheads and tool integrations (like Submittals) stay fully intact across successive re-imports.

Note

  • At this time, the latest cloud versions of P6 .xer files are not supported.

Steps

Re-Importing Schedules

  • As your project progresses, you can upload updated versions of your Read-Only schedule using the Import button again.

  • Importing a new schedule file completely overwrites and replaces the previously uploaded schedule—it does not append or add to the existing data.

  1. Navigate to the project's Scheduling tool.

  2. Click Import Ready Only Schedule.

  3. Click Attach File(s) and select your schedule file, or drag-and-drop the file into the upload area.

  4. Click Import.

Updating Existing Schedules

When updating an existing schedule file in your third-party scheduling software (e.g., Microsoft Project, Primavera P6, Phoenix):

  • Always use Save to update your file. This preserves the internal activity IDs needed to map existing Lookahead activities in Procore.

  • Do not use Save As. Using Save As creates a brand new schedule file with new internal IDs. Attempting to upload a Save As copy into Procore will trigger an error because it breaks the associations with your project's Lookahead activities.

See Also

Loading related articles...