Relaunch Online Portal Checklist
An online portal (e.g., customer portal, member area, intranet) requires special attention to security, user roles, and data migration.
Phase 1: Strategy & Planning
Before the relaunch, goals, requirements, and framework conditions must be clearly defined.
Goals and requirements
- Define project goals (e.g., more users, better usability, new features)
- Set KPIs (e.g., registrations, login rate, conversion, dwell time)
- Analyze stakeholders and target groups
- Define user requirements and user journeys
Project organization
- Define the project team and responsibilities
- Create a project plan and milestones
- Plan the budget and resources
- Identify risks and dependencies
Technical planning
- Select the technology stack and CMS/portal platform
- Define the hosting and infrastructure concept
- Plan interfaces (API, CRM, ERP, etc.)
- Define security and data protection requirements
Phase 2: Information architecture & UX
The portal must offer a clear structure and intuitive navigation.
Structure and navigation
- Define information architecture
- Plan navigation structure
- Model user flows and processes
UX/UI design
- Create wireframes
- Define design system and UI components
- Implement responsive design (mobile first)
- Consider accessibility
Branding
- Integrate corporate design
- Define imagery and typography
- Ensure brand recognition
Phase 3: Content & data migration
When relaunching an online portal, content and data must be transferred carefully.
Content management
- Perform a content audit (analyze all content)
- Update or recreate content
- Adapt content structure to new information architecture
Data migration
- Migrate user accounts and profile data
- Transfer documents and media
- Ensure data integrity
SEO & metadata
- Define meta titles and descriptions
- Store ALT texts for images
- Develop keyword strategy
Phase 4: Development & Integration
The technical implementation of the online portal takes place in a controlled development environment.
Development environment
- Set up DEV and staging environments
- Implement version control (e.g., Git)
Development
- Develop front-end components
- Implement backend logic and portal functions
- Set up user roles and rights management
System integration
- Integrate APIs and external systems
- Implement authentication systems
- Integrate payment or service interfaces (if relevant)
Phase 5: SEO, Tracking & Analytics
Measurability and visibility must be ensured before launch.
SEO
- Define URL structure
- Set up 301 redirects from old URLs
- Create XML sitemap
- Configure robots.txt
Tracking
- Define tracking concept
- Implement analytics tools
- Set up conversion tracking
Data protection
- Integrate cookie consent solution
- Provide GDPR-compliant privacy policy
Phase 6: Quality assurance & testing
The portal must be thoroughly tested before launch.
Functional tests
- Test user registration and login
- Check workflows and functions
- Test forms and interfaces
Usability tests
- Obtain user feedback
- Identify UX problems
Technical tests
- Perform cross-browser tests
- Optimize loading times
- Perform security checks
- Check HTTPS encryption
Phase 7: Launch / Go-Live
The relaunch should be structured and, if possible, take place outside of peak usage times.
- Create a backup of the old system.
- Migrate the database and files.
- Switch the domain to the new environment.
- Activate redirects.
- Check tracking.
- Submit the XML sitemap to search engines.
Phase 8: Post-launch monitoring and optimization
After the relaunch, continuous optimization begins.
Monitoring
- Monitor system performance
- Analyze errors and crawling problems
- Observe traffic and user behavior
Optimization
- Collect user feedback
- Perform A/B tests
- Implement conversion optimization
Maintenance
- Perform security updates
- Schedule backups
- Update content regularly