Pisano Cloud Hosting and Data Storage Region Change

If you are considering a region change, the sections below explain what the migration involves, which configurations and integrations may be affected, how data migration is handled, and what to consider before planning the change.

What You Will Find Here

This article covers:

• Integration
• Data Driven Content
• Operational Processes
• Summary
• Recommendation
• Frequently Asked Questions

Integration

Pisano environments in different regions are operated as separate application environments. Each environment has its own database, account configurations, network settings, and integration endpoints.

Moving an existing customer account to another region requires the target environment to be prepared. Several configuration items need to be recreated or revalidated as part of the migration, including:

• Account level settings
• Users and permissions
• IP allowlists
• Integration configurations
• API endpoints
• SFTP and FTP connections
• Email or communication provider settings
• Authentication configurations
• Other environment specific parameters

Data Driven Content

Data driven content stored in the existing environment can generally be migrated through controlled database export, import, or migration procedures. 

This may include:

• Surveys
• Feedback records
• Other relevant application data

The migration requires additional technical analysis, data validation, and migration effort to ensure data integrity and consistency between the source and target environments.

Configuration and integration components cannot always be transferred purely at database level. Many of these components depend on environment specific credentials, URLs, network rules, certificates, or external systems. These components therefore need to be configured again for the new region when required.

Operational Processes

From an operational perspective, all active processes should be treated similarly to a new environment deployment.

Existing survey distributions, workflows, automated jobs, web integrations, APIs, and other integrations need to go through design verification, configuration, testing, and User Acceptance Testing in the target environment before production cutover.

External systems may also need to update:

• Endpoint URLs
• Firewall rules
• IP allowlists
• Credentials
• Integration configurations

Depending on the architecture, a short controlled cutover window may be required to avoid duplicated transactions, missed data, or inconsistencies between the two environments.

Summary

The overall migration duration and effort depends on:

• Account size
• Historical data volume
• Number and complexity of integrations
• Number of active surveys and workflows
• Authentication setup
• Customer-specific configurations

As regional migration involves additional professional and technical services beyond standard platform operation, the required effort and any associated cost need to be assessed based on the actual scope at the time of the request and agreed separately. 

Recommendation

 We recommend selecting the most appropriate hosting region at the beginning of the project based on expected: 

• Regulatory requirements
• Data residency requirements
• Security requirements
• Integration requirements

A later change remains possible, but stakeholders should consider that it involves additional implementation effort, testing, coordination, and potentially additional cost.

The change should therefore be treated as a planned migration project rather than an instantaneous or configuration only change.