KENYA · GUIDE 0598 · EDITION 4.2
Website content migration in Kenya: Risks and Launch Plan
Set the conditions for a safe commercial test
- Broken links
- lost media
- unauthorized copying
A migration looks complete while losing customer value when old links lead nowhere or downloadable forms disappear despite the main navigation appearing correct.
A risk list is useful only when it changes a decision. For each risk, write the observable warning, who checks it and the response before the next commitment. Do not treat a reserve of money as permission to continue unsafe or unauthorized work.
Use a small, measurable pilot
Migrate a small representative page set into staging.
The pilot scope is: Migrate approved pages and assets using a source-to-destination inventory, preserving essential links, document access, content ownership, and agreed handling of obsolete material.
| Gate | Evidence before continuing |
|---|---|
| Scope agreed | Migrate approved pages and assets using a source-to-destination inventory, preserving essential links, document access, content ownership, and agreed handling of obsolete material. |
| Output acceptable | Ask the owner to compare priority journeys before and after migration, checking images, downloads, internal links, forms, and content that should remain unpublished. |
| Costs recorded | Include inventory, content cleanup, asset transfer, formatting repairs, redirect planning where relevant, quality review, and coordination of a suitable final publication window. |
| Buyer response recorded | Keep source mappings, asset permissions, excluded pages, broken-link findings, destination checks, approval records, and remaining items requiring a content-owner decision before release. |
Stage the launch around prerequisites
First confirm the buyer specification and activity requirements. Then compare suppliers, establish suitable facilities and prepare the operating record. Run the bounded trial when those prerequisites are in place. Review actual costs, quality failures and cash collected before increasing the commitment.
This sequence is not a promise that the complete business cycle fits into 30 days. Growing periods, qualifications, approvals, seasonal access and customer buying cycles can require longer. Revise the schedule when a prerequisite changes rather than skipping it to meet a launch date.
Choose continue, revise, pause or stop
Continue only when the scoped result is accepted and direct costs and payment timing are workable. Revise one part of the offer if the problem is identifiable and affordable to test again. Pause when required information, permission, skills or resources are missing. Stop the affected work when safety, consent or lawful authority is uncertain.
Keep a maximum test loss and unpaid-balance limit suited to your actual funds. A successful single delivery is useful evidence, but it does not establish year-round demand or justify committing every available resource.
Tie launch milestones to observable checks
| Risk signal | Evidence to inspect | Response to test |
|---|---|---|
| Images missing | Compare media paths/rights and import log. | Restore correct assets and recheck references. |
| Redirect loop | Inspect source/target chains. | Correct mapping before release. |
| Copied form contacts real clients | Check destination integrations. | Disable side effects and use fictional tests. |
Outstanding go / hold conditions
- Actual sites, export compatibility and redirects unverified.
- No content or DNS moved.
Assign an owner, evidence reference and review date to each unresolved condition. Do not give every milestone a fixed calendar date when it depends on a crop, production, approval or competence cycle. Run only a suitable limited trial, reconcile accepted output and actual cash, and record whether the evidence supports holding, revising, proceeding within the limit or stopping.