back to work case study · client project · live

Dream Sails: a complete WordPress migration.

I rebuilt a sailing holiday website while preserving its offers, history, mail, and the ways customers get in touch. The new site is now live on the client's domain.

Astro + SanityCloudflarefirst-party formsSEO migration
Dream Sails homepage after its October 2026 launch.
dreamsails.ro
starting point

A crowded WordPress site.

The old site mixed real vacations with theme demo pages, plugins, and content that was hard to maintain. Its forms sent visitors away from the website.

what mattered

More than the design.

Offers, galleries, testimonials, and URLs known to search engines had value. The existing mailboxes and separate sailing course site also needed to keep working.

result

A new site on the real domain.

Dream Sails now runs on Astro and Cloudflare Pages. Vacation content is edited in Sanity, with separate environments for review and publication.

controlled migration

Inventory first. Platform change second.

I archived the public pages and kept a verified backup of the legacy hosting account, including both WordPress installations and databases. That evidence helped separate real business content from leftover theme material and check each migration decision.

Seven genuine legacy vacation pages kept their URLs. Renamed pages received deliberate redirects, and relevant old images were handled explicitly. Unrelated demo pages were not sent to misleading destinations.

01Public archive and legacy hosting backup.
02Inventory of content, URLs, images, and forms.
03Astro rebuild with structured Sanity content.
04QA, launch checks, and move to the client's domain.
content

Editable vacations without a page builder.

Dates, prices, galleries, itineraries, and map stops have dedicated fields in Sanity. QA and production use separate workspaces so changes can be reviewed before reaching the public site.

enquiries

Forms that belong to the site.

Contact and vacation requests use validation, spam protection, and delivery through a private SMTP service. Vacation requests also go into a protected register; email remains a fallback.

operations

Access and recovery documented.

A private hub brings together administration links and the request register. Verified copies of the code, Sanity content, and form databases have documented restoration steps.

behind the scenes

The site moved. Mail kept working.

I separated website DNS from the records used by the existing mailboxes. Cloudflare serves the website while iHosted continues to host mail. The sailing course site stayed on its own infrastructure.

Form delivery changed during the project: the first email route responded too slowly for the client's addresses. I switched to authenticated SMTP and verified message acceptance before launch. Newsletter subscriptions use MailerLite, separately from contact and vacation requests.

01Sanity for vacations and editable content.
02The existing inbox for enquiries and replies.
03A private register to track booking requests.
04MailerLite for subscribers and unsubscribes.
Live Dream Sails homepage.
dreamsails.ro
The live homepage with the new visual direction and the client's content.
Live Dream Sails vacation listing.
dreamsails.ro/tours
Vacations are easy to browse, and their details are editable in Sanity.
Live Dream Sails vacation enquiry form.
dreamsails.ro/rezervare
Visitors can send a request on the site without an external form.
outcome

A completed launch with a clear way to run the site.

Dream Sails now has a public website, editable vacations, on-site enquiries, and a documented process for publishing and recovery. The project still receives refinements, but the WordPress migration and move to the client's domain are complete.

I want a simpler website