Skip to main content

HoopAI Migration

Website migrationMove the website with launch risk visible.

Move an eligible website into HoopAI with a page inventory, redirect plan, validation pass, and explicit exception log.

01

Mapped before movement

Inventory the source, destination, volume, ownership, and failure cases first.

02

Controlled cutover

Sequence redirects, validation, permissions, and launch checks around one plan.

03

Visible exceptions

Record what moved, what changed, what did not move, and who owns the remainder.

The job behind the service

The migration is finished when the destination works, the redirects resolve, and the exceptions have owners.

What the engagement covers

A scope people can read before they sign.

Every engagement names the work, owners, limits, timing, and handover so expectations stay visible.

  1. 01

    Page and asset inventory

    Defined against the agreed operating job and acceptance check.

  2. 02

    Up to 150 eligible pages

    Defined against the agreed operating job and acceptance check.

  3. 03

    Redirect and launch checklist

    Defined against the agreed operating job and acceptance check.

  4. 04

    Validation and exception log

    Delivered with the open limits, decisions, and next owner recorded.

How the work moves

Structured enough to trust. Human enough to adapt.

The delivery path stays consistent while the details follow the system, team, and outcome in scope.

  1. 01

    Align the outcome

    We name the operating job, owner, boundaries, dependencies, and acceptance checks before delivery starts.

  2. 02

    Map the system

    We inspect the data, permissions, workflows, integrations, and team habits that the new setup must support.

  3. 03

    Build and verify

    We configure the agreed scope, test the real workflow, and resolve launch blockers against the acceptance plan.

  4. 04

    Handover the work

    We train the owners, document the operating path, and make open limits visible before the engagement closes.

A human handover

The people doing the work should leave stronger.

Each principle is built into scoping, working sessions, verification, and the final handover.

HoopAI delivery principle

Clarity

The owner can explain the workflow and its boundaries.

HoopAI delivery principle

Practice

The team works through the real path before handover.

HoopAI delivery principle

Continuity

Open risks, limits, and next actions keep their owners.

“The work is finished when the operator can run it, the system can be checked, and the remaining limits have owners.”
HoopAI delivery standard

Related HoopAI customer story

Evidence from work already in the field.

This published customer story is related to the service area. It is shown as real HoopAI evidence, not as a promise of identical results.

A dashboard showing service request forms, interactive journey steps, agent responses, work orders, and invoices tied to yacht profiles and locationsRead the full story

Ebhar

Managing nationwide yacht services with AI assistance

“"Knowledge is reusable, handoffs are clean, and we can iterate weekly without waiting on external teams."”
Anthony GreenProduct Lead of Ebhar
239%
Lead Volume Increase
450%
Faster Response Time
82%
On‑time Completion

Ebhar transformed how yacht owners request services and receive updates. A single Hoop site captures requests, the AI assistant answers and routes, and operations run with clear workflows, dashboards, and billing. Customers see faster responses and reliable follow‑through.

Open customer story

Project pricing

Website migration

The total is the setup price plus the number of eligible pages in the signed inventory.

Prices exclude applicable taxes and third-party costs. The signed scope controls the final deliverables, timing, eligibility, and acceptance criteria.

Before kickoff

Inputs and limits stay visible.

Useful service design shows what each side brings and where a separate scope begins.

Engagement facts

Capacity
Up to 150 eligible pages
Typical window
2 to 4 weeks
Price
$500 setup + $20 per page

What we need from you

  • A named executive sponsor and day-to-day owner
  • Timely access to the systems, data, and people in scope
  • Decisions and feedback inside the agreed review windows
  • An accessible live or staging source site and a signed page inventory

Outside the standard scope

  • Third-party license, media, travel, and vendor costs
  • Work outside the signed scope or acceptance criteria
  • Unlimited revisions, requests, or ongoing implementation
  • Graphic design, substantial custom development, content strategy, major restructuring, and unsupported third-party functionality

Questions before the scope

Clear answers before work begins.

Bring the unusual edge cases into the scoping conversation. The written agreement should carry the answer.

01How is the website migration price calculated?

The price is a $500 setup fee plus $20 for each eligible page in the signed inventory, up to a maximum of 150 pages.

02What does Website Migration exclude?

It excludes graphic design, substantial custom development, content strategy, major restructuring, and unsupported third-party functionality. Those needs require a separate scope.

03How is the final scope confirmed?

We confirm the outcome, systems, volume, owners, dependencies, exclusions, timeline, and acceptance checks in writing before delivery begins.

04Can the scope change after kickoff?

Yes. We document the change, its effect on price and timing, and the revised acceptance check before adding it to the engagement.

05Does the price include third-party costs?

No. Software subscriptions, paid media, travel, data vendors, and other third-party charges are separate unless the signed scope says otherwise.

Start with the job

Plan the next move with the scope visible.

Bring the job, systems, constraints, and deadline. We will turn them into a bounded scope with a clear path to handover.

Talk to sales
Need help choosing? We will route the job to the right service path.