Intranet Migration & Implementation Services

When migrating an intranet, it’s crucial to consider data integrity, user adoption, and continuity of services. Ensure all content is correctly mapped and transferred, assess the impact on users, and plan for training and support. Also, consider the technical compatibility between the old and new systems, and have a clear rollback plan in case issues arise during the migration.

An intranet migration plan should include the following components:
• Assessment: Evaluation of the current intranet and identification of what needs to be migrated
• Data Mapping: Clear mapping of how content and data will transfer to the new system
• Timeline: A detailed schedule with key milestones and deadlines
• Training: Plans for user training and support during and after the migration
• Testing: Thorough testing phases to ensure everything works as expected post-migration
• Rollback Strategy: A contingency plan in case the migration encounters significant issues

Implementing a new intranet typically takes between 3 to 6 months, depending on the complexity of the platform, the level of customization required, and the size of the organization. This timeframe includes planning, design, development, testing, and user training.

Migrating an existing intranet to a new vendor generally takes 2 to 4 months. The timeline can vary depending on the amount of data being transferred, the complexity of the systems involved, and the need for customization or reconfiguration during the migration.

The best reasons to consider an intranet migration include outdated technology, lack of support from the current vendor, the need for better integration with other tools, poor user adoption, and the availability of more advanced features or a more user-friendly platform. Migrating can also be driven by changes in business needs, such as scaling up or down, or the desire to improve security and compliance.