Customer data platform (CDP) deployment readiness checklist

Transmitted over TLS · Stored encrypted at rest · Reviewed only by PrivyCDP architecture and partner DevOps leads under NDA. Need to talk to a human first? Request a architecture review with engineers →

What to prepare before completing the checklist

• Identify the proposed cloud account or datacenter and the person who can assess prerequisites.
• Map sources, data categories, identity rules, destinations and allowed network paths.
• Record access, backup, incident and upgrade owners, including unresolved responsibilities.
• Use measured normal and peak workload assumptions where available; otherwise record unknown.

How to use the result

The checklist organizes readiness questions for an architecture discussion. Review each unanswered item with its owner and distinguish an assumed prerequisite from a verified environment. A completed checklist is not production authorization, a security approval or a promise that a connector is supported. Retain the proposed release, deployment boundary and operating assumptions with any pilot result.

What happens next

Use the result to choose the smallest useful evaluation. Agree one synthetic source-to-destination flow, obtain the required contracts and test permissions, identity changes, retries and recovery. Ask what evidence would change the decision to proceed, revise or stop. Assign responsibility for missing data and environment access rather than treating a form response as validation.

The review agenda explains the conversation, while the intake form collects the initial request. This checklist concentrates on environment and operating readiness. Do not include credentials, real customer records or unnecessary sensitive details. Any commercial, legal or production decision remains a separate review against the actual scope.