What we can work on.
Your written proposal identifies the actual setup, accounts and functions involved. The starting process is:
Map the existing site
Record the relevant pages, forms, assets and integrations. Identify URL behavior, access requirements and what the move needs to preserve.
Prepare and test the destination
Create an appropriate copy or backup where access permits, configure the destination and verify the agreed content and functions before switching.
Coordinate the cutover
Plan DNS changes around existing website and email records. Verify HTTPS, agreed URLs, redirects and forms, and document any remaining work.
Scope and separate costs.
A migration quote depends on the source platform, content, available access and destination. A redesign, complex platform conversion, mailbox migration, malware cleanup and recovery of inaccessible accounts are separate. A cutover can involve propagation or interruption; zero downtime and unchanged search rankings are not guaranteed.
We agree on the work, price, responsibilities and scheduling before making changes. Larger development work and recurring support are separate scopes.
Common questions.
Will you preserve my URLs?
The migration scope should include a URL inventory and redirect plan where needed. We identify changes before the move and verify the agreed destinations afterwards.
What about business email?
Existing email records need to be identified before DNS changes. Moving mailbox contents is a separate project and is not implied by a website move.
Can you move a WordPress site?
Yes, subject to the site, theme/plugins, available access and destination requirements. Share the URL and provider names so I can assess the scope.
What to send me.
Send the website URL, your current provider names, what you want to change and any timing constraints. We can clarify the requirements by email before a written proposal.
Request a written proposal ↗