Move an existing website
Plan a move between hosting providers or platforms, covering the agreed content, assets, data and domain changes. Identify redirects, testing and a rollback approach before switching over.
S06 / BESPOKE DEVELOPMENT
Some projects begin with an existing website, a disconnected workflow or a system that has become difficult to maintain. We assess what is there and define a practical piece of work.
Move, connect or improve the systems you already depend on.
Discuss your project
Bespoke scope, pricing and delivery. Speak to customer support for an assessment.
POSSIBLE USE CASES
Make the next change a considered one.
These are examples to discuss, rather than a fixed package. The features and deliverables depend on your project.
Modernise a legacy system
Review an older codebase, replace agreed components or rebuild a specific workflow in stages, with dependencies and continuity needs considered before changes begin.
Connect business tools
Link a website or application to a CRM, booking platform, stock system or payment provider through available APIs, with agreed data flows and error handling.
Reduce repetitive administration
Replace manual copying between spreadsheets, forms and systems with a scoped import, reporting tool or automated workflow, including checks for incomplete or duplicate data.
DEFINE THE WORK
Agree the details before development.
Understand the current setup
Review the relevant code, accounts, data, licences and supplier constraints. Confirm what can be accessed or moved and whether paid discovery is needed before implementation can be quoted.
Define the change and its boundaries
Agree the deliverables, integrations, migration mapping and exclusions. Record dependencies, third-party charges and any work that requires the original supplier’s involvement.
Check, switch over and hand over
Agree backups, validation, acceptance and any cutover or rollback plan appropriate to the project. Set out documentation, source-code handover and ongoing support separately.
PROJECT DELIVERY
A clear process, shaped to the project.
- 01
Discuss and assess
Tell customer support about the users, current systems, required features and preferred timing. We assess feasibility and agree any discovery work and its cost first.
- 02
Agree the project
Confirm the scope, price, payment stages, milestones, dependencies, revisions, acceptance checks and handover arrangements in writing before development starts.
- 03
Build and review
Develop the agreed work, review it at the planned stages and assess changes to scope, cost or timing before additional work proceeds.
- 04
Accept and hand over
Complete the agreed acceptance checks and release or migration steps. Provide the agreed code and documentation, and arrange ongoing support if required.
COMMON QUESTIONS
Before we begin.
Can you migrate a website built by someone else?+
We can assess the move. Share the current website, platform and intended destination. The approach depends on access, export options, data and licensing. We confirm what can be migrated, any rebuilding required and the scope before work begins.
What if I only need one integration or a small improvement?+
A project can focus on a specific change. Describe the workflow, systems involved and expected result. We assess feasibility and agree a proportionate scope and quote; a complete rebuild is not a prerequisite.
How is this different from website repair and takeover?+
Website repair focuses on diagnosing faults and organising ongoing responsibility. A customised development project covers a planned change such as a migration, integration, modernisation or new workflow. We can help clarify the right starting point during your enquiry.
Do standard website delivery terms apply?+
The standard website subscription delivery provisions do not apply to customised development projects. Contact customer support to agree the assessment, price, scope, milestones, revisions, acceptance and handover in a written project agreement. Other applicable Terms of Service continue to apply.
LET’S DISCUSS IT
Start with the problem you want to solve.
Share the main users, features, existing systems and any preferred timing or budget. Customer support will help clarify the assessment and next steps before a project scope and quote are agreed.