Best practices for moving surveys, workflows, and dashboards from Staging to Production | Experience Community
Skip to main content

Best practices for moving surveys, workflows, and dashboards from Staging to Production

  • April 21, 2026
  • 3 replies
  • 60 views
Z
Level 2 ●●
Forum|alt.badge.img+2
  • zzh
  • Level 2 ●●

Hi everyone,

We’re currently working with separate Qualtrics instances (Staging and Production), and I’m looking for recommended or proven approaches to reliably transfer assets between them.

Specifically, I’m interested in experiences and best practices around moving:

  • Surveys (including Survey Flow, Embedded Data, JS customizations)
  • Workflows (events, conditions, code tasks, email tasks, integrations)
  • Dashboards / Reports (sharing settings, widgets, filters, permissions)

Some concrete questions I’m hoping the community can help with:

  • What is the preferred way to promote surveys from Staging to Production?
    • Copy project → export/import → other?
    • Any common pitfalls to watch for (IDs, embedded data dependencies, look & feel, etc.)?
  • How do people typically handle Workflows, given that they are tightly coupled to surveys, events, and environments?
    • Manual recreation vs. templates vs. API‑driven approaches?
  • Are there recommended patterns for keeping Staging and Production aligned over time (naming conventions, versioning, documentation, checklists)?
  • For dashboards, is rebuilding still the norm, or are there better options people are using successfully?

We’re aiming for a controlled, repeatable promotion process (similar to what you’d expect in a standard SDLC), but Qualtrics doesn’t seem to have a fully supported “deploy” mechanism across instances.

Any insights from:

  • Qualtrics product team members
  • Partners / agencies
  • Or customers managing multi‑environment setups

would be greatly appreciated.

Thanks in advance!

    3 replies

    Lpena
    Qualtrics Employee
    Forum|alt.badge.img+4
    • Lpena
    • Qualtrics Employee
    • May 13, 2026

    Managing the move from Staging to Production in Qualtrics can definitely be a bit of a puzzle since there isn't a native "deploy" button just yet. For surveys, sticking to QSF exports or using the API is usually the safest bet, but you really have to keep an eye on those embedded data dependencies and any custom JavaScript that might break with new IDs. Workflows are a bit more high-maintenance and often require manual recreation or some clever API work to stay consistent. If you're dealing with dashboards, the CX Project Cloner is a lifesaver for duplicating those resources, though you’ll still want to double-check your ownership permissions during the handoff. Keeping everything aligned usually comes down to strict naming conventions and a solid promotion checklist.

    Since cross-instance migrations can get pretty technical and involve some backend complexities with brand permissions, it might be worth having an expert take a look at your specific setup. You can get in touch with the support team by logging into the https://support-portal.qualtrics.com/ and opening a ticket under the technical support section. They can help ensure nothing gets lost in translation between your environments!

    This reply contains AI usage for clarity and language purposes.
      Z
      Level 2 ●●
      Forum|alt.badge.img+2
      • zzh
      • Author
      • Level 2 ●●
      • May 18, 2026

      ​@Lpena 

      Thanks for your reply.

      Can you please provide more info on the CX Project Cloner that you mentioned. Is this a third-party tool? I couldn’t find it in the Qualtrics documentation.

      J
      Level 2 ●●
      Forum|alt.badge.img+5

      As mentioned, there is no button to deploy a test across the entire brand; work is always done directly on the live project. In my case, this depends on the type of survey.

      Once all testing is completed and everything works as expected, that same project is promoted to production. I only remove the test responses.

      Additionally, I create a copy of the project to work from, which helps prevent accidental deletion of workflow configurations or issues with embedded data.

      If the project is shared with another user who has administrator permissions, before making any requested changes — or if any issues arise — I review the survey version and select the correct one to eliminate any unintended modifications before starting work.

      In some areas, you can save templates to streamline the process; for example, in ticket management, where templates allow you to reuse configurations instead of building everything from scratch.

      Terms & ConditionsAccessibility statement