Palantir Foundry Migration and Cutover

Overview

Migrate contracts and evidence, not just bytes. Inventory data semantics, identities, access controls, pipeline transactions, Ontology entities, applications, and operational dependencies before dual-running a bounded slice.

Prerequisites

• Name source and target owners, business workflows, datasets, schemas, identities, controls, service objectives, retention, and rollback deadline.
• Choose the target Foundry primitives: connectors, transforms, Ontology resources, OSDK application, DevOps product, or Compute Module.
• Read references/official-docs.md and document features or resources that do not map directly.
• Establish a frozen baseline and approved non-production landing zone.

Current Contract

• Foundry applications and resources can be packaged and promoted with DevOps and Marketplace across environment spaces.
• Developer Console application installation remaps supported parameters, but API-name consistency and dependencies still require explicit handling.
• Incremental transforms have transaction-history requirements and must reconcile with snapshot behavior.
• Access control combines project roles, mandatory controls, Ontology policies, and application restrictions.