Overview
By integrating Fieldwire with Oracle Primavera P6, you can manually import and update your Fieldwire tasks using a Primavera P6 planning file (.xml). This guide walks you through how to use this integration to efficiently sync task data between Primavera P6 and Fieldwire.
Like the integration between Fieldwire and Microsoft Project, to use this integration with Primavera, simply go your project and click on Import tasks.
Note: For general questions or issues related to Primavera P6, please contact Oracle support directly. Fieldwire Support can assist with issues occurring within Fieldwire.
Demo Video
Fieldwire Requirements
- Requires a Business or Business Plus license
- Must be an Admin on the Fieldwire project
How to Import Tasks from Primavera P6
To use this integration, navigate to your project and import a Primavera P6 (.xml) file. This will create new tasks and update existing ones in Fieldwire.
Setup Requirements in Primavera P6
To fully leverage this integration, ensure the following custom fields are created in Primavera P6:
- Fieldwire email
- Fieldwire category
- Fieldwire status
Important:
- These must be created as user-defined text fields
- Use the exact field names shown above (case-sensitive)
- These fields enable mapping to Fieldwire task attributes
How to Export a Primavera P6 (.xml) File
- Open your Primavera P6 project
- Click File
- Click Export
- Select Primavera P6 (XML)
- Click Next twice
- Uncheck checkbox next to "Export all project layouts to a compressed file"
- Click Finish to complete the export to generate the .xml file
Import Steps
- Navigate to the Tasks tab
- Click + Import Tasks
- Select Primavera P6 (.xml)

Next:
- Upload your .xml file
- Review the confirmation modal:
- Tasks to be created
- Tasks to be updated
- Tasks to be deleted
- Click Next

What Happens During Import
- Tasks are created or updated based on the Primavera P6 Object ID
- Tasks removed from the .xml file are moved to Trash
- Only leaf-level tasks are imported (no parent/summary tasks)
- If multiple projects exist in the .xml file, only the first project is imported
Note: All changes are recorded in each task’s history log.
Field Mapping (Primavera P6 → Fieldwire)
| Primavera P6 Field | Fieldwire Field | Required? |
|---|---|---|
| ObjectId | Primavera P6 Object ID | Yes |
| Activity ID | Primavera P6 Activity ID | Yes |
| Activity Name | Task Title | Yes |
| Start | Start Date | No |
| Finish | End Date | No |
| Fieldwire email | Assignee | No |
| Fieldwire status | Status | No |
| Fieldwire category | Category | No |
Note: Tasks without a name are not imported.
Key Behaviors
- Create & Update: Matching Object ID → task updated; otherwise created
- Empty values: Do not overwrite existing Fieldwire data
- Deletion: Removed tasks are moved to Trash
- Hierarchy: Only lowest-level tasks are imported
- Multiple projects: Only the first project is processed
- Source of truth: Primavera P6 overrides Fieldwire when non-empty values exist
Limits
- Maximum 1,000 tasks per import
- Maximum 10 imports per day per project
Error Handling
- No tasks found: No importable activities
- Too many tasks: Exceeds 1,000 task limit
- Invalid assignee: Email does not match a project member
- Invalid category: Category does not exist
- Invalid status: Status is not valid
- Unknown error: File parsing failed
Note: Errors reference tasks by Activity ID (alphabetical order).
Post-Import Behavior
- Success message: "Tasks imported successfully"
- Triggers standard Fieldwire notifications (web, mobile, email)
- Tasks sync to mobile and remain fully editable
Test the Integration!
- Create a new project
- Go to the Tasks tab
- Import a Primavera P6 (.xml) file
- Review task creation, updates, and deletions
FAQs
What information can be uploaded?
The following information is synced with P6:

- Note: Fieldwire email, status, and category are custom columns that need to be created in P6. More information in our demo video.
How does this integration handle hierarchy and relationships?
Parent tasks and relationships are not imported. Only leaf-level tasks are supported.
Can this integration update and delete my Fieldwire tasks?
- Yes!
- If you update a task in P6, it will be updated in Fieldwire.
- If you delete a task in P6, it will be deleted (trash) in Fieldwire.
- If you restore it or unarchive it, it will be restored in Fieldwire.
I changed a task in Fieldwire. Will that be erased?
If the information is different in P6 and you import a new .xml file with a different, non-empty value, then yes, the information in Fieldwire will be erased. P6 is considered as the source of truth.
Example
Your Fieldwire task is:
- Title = “Title 1”
- Assignee = assignee@email.com
- Category = “Category 3”
- Start and end date = 1/1/2025 - 1/1/2025
If you import a .xml where this task is:
- Title = “Title 20”
- Assignee = (null)
- Category = (null)
- Start and end date = 3/3/2025 - 3/3/2025
Then the result will be:
- Title = “Title 20”
- Assignee = assignee@email.com
- Category = “Category 3”
- Start and end date = 3/3/2025 - 3/3/2025
How frequent is the refresh?
This is not a live sync. Updates occur only when a new .xml file is uploaded (max 10 .xml per day).
How many tasks can be imported?
Up to 1,000 tasks per import.
I made a mistake, what should I do?
Upload a corrected or previous .xml file to restore tasks to their prior state.