Project delivery
Procore
Available
Project migration import: read one source project at a time into an os.construction project, with a dry run first.
Available today through project migration import. Step-by-step instructions are in the product guide.
Coverage by service or edition
Project migration import. Each service needs its own permissions and acceptance checks.
Procore
Available
Project migration import: read one source project at a time into an os.construction project, with a dry run first.
Ongoing read sync
Planned
Scheduled read of projects, RFIs, submittals and commitments. Planned.
Before you start
Have these ready before you start.
- A source access token for the project you are importing. It is used for that run only and is not stored.
- Confirm the destination company/project and the reviewer responsible for checking imported records.
Confirm the scope
A source access token for the project you are importing. It is used for that run only and is not stored.
Agree the mapping
Project ID → project; RFI subject → title; punch ID/name/due_date → source key/title/due date.
Preview and reconcile
Keep source identity/revisions separate from locally owned permissions, project placement and workflow decisions. Unresolved associations or conflicting local edits require review.
Review before applying
An authorized reviewer must confirm destination scope, unresolved records and control totals. A successful extraction is not proof that data has been applied.
Check recovery and access
Pause on expired or revoked access. Restore authorization before resuming from the last complete checkpoint. An incomplete list or permission error is not proof of deletion; inspect uncertain outcomes before retrying.
Mapping and synchronization
- Record mapping
Project ID → project; RFI subject → title; punch ID/name/due_date → source key/title/due date.
- Sync boundary
- Versioned REST page/per_page lists. Migration is not continuous sync.
- Source ownership
- The provider remains authoritative for its source records. Local project placement, access and workflow decisions need explicit destination ownership. Match by scoped IDs, not names alone.
- Outbound policy
- No provider business writes are offered here. Sending, posting, inviting, deleting and permission changes require separately approved capabilities.
Conflicts and recovery
When records disagree
Keep source identity/revisions separate from locally owned permissions, project placement and workflow decisions. Unresolved associations or conflicting local edits require review.
When a run stops
Pause on expired or revoked access. Restore authorization before resuming from the last complete checkpoint. An incomplete list or permission error is not proof of deletion; inspect uncertain outcomes before retrying.
Limits to plan around
- One-time or repeated migration of supported tools (directory, RFIs, submittals, punch, observations, daily logs, documents, prime contracts, commitments). Not continuous two-way sync.
- Punch assignment history and distribution are not fully preserved. Nothing is written back to the source.
No provider connection is initiated from this page. See the product guide for how to run it.
Documentation and source dates
Provider documentation establishes upstream capabilities, not os.construction availability. Confirm the current edition and API contract before planning setup.
- Procore official documentationAccessed