
Migration, Consolidation & Rebuild of 16 Websites
- or -
Post a project like this- Posted:
- Proposals: 76
- Remote
- #4518687
- OPPORTUNITY
- Open for Proposals















Description
Executive Summary & Program Purpose
This initiative encompasses the consolidation, rebuild, migration, technical integration, and SEO-preservation of 21 disparate entity web surfaces into a streamlined digital ecosystem. The scope covers 16 delivered target properties running entirely on open-source, client-owned frameworks deployed within client-managed, secure cloud environments.
Project Scope & Target Delivered Properties
The project consolidates the existing multi-website footprint into unified category-based web properties, eliminating vendor lock-in and standardizing brand assets.
The complete project details are explained in the document attached below:
https://docs.google.com/document/d/1Ntg_mV3K4c04sfN9nM0RZ0hrLQ9SCThnGLjbEh1lfOE/edit?usp=drivesdk
Imran M.
96% (37)New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-

A few basic questions before I prepare the technical approach:
~Could you confirm the preferred open-source framework/CMS for the 16 target properties—WordPress, Drupal, or another framework?
~Will the existing 21 properties remain live during the migration, and is there an existing URL/SEO redirect mapping available?
Are the 16 target properties based on a shared design/CMS architecture, or will some require substantially different functionality?
~Could you share the current technology stack, hosting/cloud environment and repository/access arrangements so we can assess the migration requirements accurately?
~What is the expected target launch date, and are the 16 properties expected to launch simultaneously or in phases?
Best,
Anuradha - Mxpertz -

- Will each entity have separate admin/editor access, or will there be a centralized administration model? Also, should shared entities such as doctors, specialties, services, branches, and locations be managed centrally and reused across multiple websites?
- What exact fields and filtering logic are required for doctors, specialties, services, and branches? Should availability come from the CMS or an external booking system, and should filtered results generate SEO-friendly shareable URLs?
- For the education/member and patient/booking platforms, is SSO required? What user information and authentication context needs to be transferred when users move between the new websites and existing external systems? -

Hi Imran,
I’ve reviewed the complete scope, including the 12 WordPress properties, 3 Laravel applications and the Shopify-to-OpenCart/Bagisto migration with Oracle integration.
Before estimating the 16-week delivery, could you confirm whether the selected vendor will receive technical discovery access/documentation for all 21 existing web surfaces and the existing Laravel applications before development begins — particularly current source repositories, database/content structures, API documentation for Oracle ERP/POS and CRM/contact-center integrations, and the existing URL/SEO inventory?
Also, are the UI/UX designs and consolidated brand/design system already prepared?
Best,
VConn Pvt Ltd