Best Practice: Establishing Content Migration Policies

Firstly, you have to decide how to deal with the Proof of Concept environment. Determine if the POC environment will transition to a development or production environment or be scrapped to start fresh.

Factors to consider:

• Assess the relevance and quality of content created during the POC phase. Define if the content created in this phase is actually useful for the Users
• Evaluate the alignment of the POC setup with long-term governance policies. Check if the access permissions, structure of content, and metadata are correct
• Ensure Data Source configurations and naming conventions comply with organizational standards of transitioning the POC environment. Check to what production tool or database the POC environment is connected

Here are some overall recommendations that will lessen the probability of losing quickly if needed. Changes to custom code (e.g., Portal Pages, Email Templates), and security model access are done in non-production

Advantages:

• Ensures vetted use cases before production implementation
• Allows for flexible ongoing maintenance in production

Risks:

• Moderate governance complexity may slow changes

This governance model ensures maximum control and compliance in regulated environments. Main features of this model are:

• Use cases are developed in a sandbox or development environment
• Thorough testing is performed in a UAT environment that mirrors production
• Only non-exportable changes are made directly in UAT
• Approved use cases are promoted to production
• No changes are made directly in production
• Upgrades are sequentially tested from lower environments to production
• One lower environment must mirror production but allow controlled changes

Advantages:

• Rigorous testing minimizes production risks
• High compliance for regulated industries

Risks:

• Potential delays in implementation due to stringent processes