Customer Voice: copying surveys across environments

Source: Claude.ai chat (original: customer-voice-survey-copy__5c5ef8c2.md) Added: 2026-10-02

Summary

• Customer Voice projects do not move through Dataverse solutions — they are copied from inside the Customer Voice app itself.
• Three mechanisms: Copy project (same tenant, Dev → Test → Prod); Update project (push later changes to an existing copy); Export / Import (cross-tenant, e.g. sandbox → client tenant).

Key takeaways

• Prerequisites in the target env: Customer Voice app installed + users have the Project Owner security role (custom roles need User-level perms on Customer Voice tables).
• Update is destructive: if a survey exists only in the target env (not in source), the Update operation deletes it. Treat Dev as master; never build directly in Test/Prod.
• Flows break after promotion: "Send a survey" / "Create an invitation" flows are hard-wired to project + survey IDs. Workaround (Amey Holden's pattern): keep project and survey names identical across environments and resolve IDs dynamically in the flow by looking up msfp_project / msfp_survey by name.
• Responses don't come across — only the design migrates. Survey IDs and links differ per environment — update any embedded URLs in emails, portals, web resources.
• Do not delete Customer Voice data directly in Dataverse — it won't sync back to the service. No msfp_* PATCH/DELETE from scripts.

Learnings / how to apply

• Add a manual "Customer Voice: Copy or Update project to target env" step to the Praxisis promotion checklist after push.ps1.
• Log the source → target project mapping in deploy/ so promotions stay traceable.
• Codify the "names identical across envs" convention in the Sustain Operating Model as the way to make Customer Voice survive promotions.

---