Agent skill · software engineering · jeremylongshore
procore-migration-deep-dive
Plan and execute a resumable Procore data migration with dependency ordering, stable origin identifiers, sync actions where supported, file transfer, checkpoints, reconciliation, and rollback. Use when importing or exporting construction records at scale. Trigger with: "migrate data to Procore", "build a Procore backfill", "reconcile a Procore migration".
Why this skill is useful
Provides specific API call patterns and error handling for Procore's REST API that the AI wouldn't reliably generate on its own.
What it needs
Requires procore account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Procore Resumable Data Migration Overview Move records as an ordered, observable, and reversible program rather than a bulk request loop. Use documented resource contracts, stable external identity, supported sync actions, and separate file workflows while preserving tenant and project boundaries. Prerequisites Source and target owners, data classification, retention, and legal approval Resource inventory, volume, dependency graph, field mapping, and unsupported-feature list DMSA or user permission map, rate budget, checkpoint store, and rollback boundary Instructions Step 1: Profile and map Count records and files by company, project, resource, status, and dependency. Map required fields, codes, users, locations, permissions, timestamps, and external identifiers. Step 2: Design stable identity Use documented originid or equivalent only where the resource supports it. Define source-to-Procore mapping, collision handling, and a replay-safe uniqueness rule. Step 3: Order dependencies Create prerequisite company and project data before dependent records. Follow documented API call sequencing and isolate unsupported resources for explicit disposition. Step 4: Execute resumably Process bounded batches, follow rate headers, checkpoint after verified commits, and use sync actions only for supported resources. Transfer files through their separate documented upload and association flow. Step 5: Reconcile continuously Compare counts, key fields, relationships, file checksums, failures, duplicates, and state hashes per batch. Quarantine poison records without blocking the entire migration. Step 6: Cut over and settle Run final delta capture, freeze writes if required, verify parity, switch consumers, observe, and preserve rollback until the agreed settlement window closes. Authentication Migration calls use an OAuth 2.0 Bearer token for the approved user or DMSA and explicit company and project scope. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/procore-migration-deep-dive--932871