Short answer: Scorpion says a customer who leaves after fulfilling the contract receives website static files, design assets, content, and ownership of several key marketing accounts. It also says the customer does not own Scorpion’s underlying system.[1] That handoff may preserve the visible pages and creative work, but it does not promise a portable content management system that another provider can log into and keep operating. Before signing or leaving, ask for a written handoff inventory and test whether forms, booking, tracking, redirects, and editing will work on the new host.
This article uses Scorpion’s public FAQ as a real contract-review example. It is not a legal reading of a specific customer agreement, and it is not a claim that Scorpion’s model is improper. The point is narrower: “you own the website” and “you receive a working website you can operate elsewhere” are different promises.
Source snapshot: August 25, 2026. Scorpion’s public terms can change. The signed proposal, service order, and contract control your deal.
Why this article is narrower than our Scorpion review
Our full Scorpion review for contractors covers fit, contract length, ownership, services, and alternatives. This page deals with one exit question: what can a contractor actually do with the website materials after the agency relationship ends?
That distinction matters because the official FAQ uses two sets of language. Scorpion says the customer owns the website after the contract term is complete and that domains, content, and imagery belong to the customer. It also says the customer will not own the underlying system. For a fulfilled-contract departure, the FAQ says Scorpion transfers ownership of key accounts such as GA4, Local Services Ads, social accounts, and website content, and provides static files, design assets, and content.[1]
Those are useful commitments. They still leave an operational gap that the contract should close: what runs on day one after the move?
Verified facts from Scorpion’s public FAQ
| Public statement | What it establishes | What still needs a written answer |
|---|---|---|
| The customer owns the website after the contract term is complete.[1] | Scorpion publicly recognizes customer ownership after the stated condition. | The exact transfer date, early-exit treatment, and usable delivery format. |
| Domains, content, and imagery are the customer’s assets.[1] | Important brand and publishing assets are identified as belonging to the customer. | Registrar access, original file formats, licenses, and a complete asset list. |
| The customer does not own the underlying system.[1] | Scorpion’s operating platform is excluded from the ownership promise. | Which features depend on that system and what replaces them after departure. |
| A fulfilled-contract departure includes static files, design assets, content, and transfer of several key accounts.[1] | The FAQ describes a concrete handoff beyond a bare content document. | Whether the package includes working forms, databases, integrations, redirects, and an editable CMS. |
Scorpion’s FAQ is a public summary, not the customer’s complete contract. A contractor should ask Scorpion to attach the promised exit package to the agreement as a schedule. Name every account, file type, credential, deadline, and transition duty. A sentence that sounds clear in a sales call can become surprisingly elastic when a migration is already underway.
Static files and a working CMS are not the same handoff
A static website is made from HTML, CSS, JavaScript, images, and other files that a server can deliver to a visitor. MDN notes that static sites do not have server-side logic. Each visitor receives the same prepared content for a given URL.[2]
A content management system such as WordPress adds an operating layer. It stores content and settings, lets an administrator edit pages, manages users, and connects themes, plugins, forms, redirects, schema, and other functions. WordPress’s own backup guidance treats the files and database as separate parts of a complete backup. A restorable WordPress handoff needs both.[7]
WordPress also has a built-in export tool that produces an XML file containing items such as posts, pages, comments, custom fields, categories, tags, taxonomies, and users.[6] That export is useful, but it is not the same as a full site backup. It does not, by itself, promise the original theme, plugin code, configuration, media library files, or database state needed to reproduce the current site.
There is nothing inherently defective about a static site. A properly built static site can be fast, secure, inexpensive to host, and completely portable. The problem appears when the buyer expects an editable marketing system but receives only the browser-facing output.
A simple shop-floor comparison
Static files are closer to receiving a set of finished cabinet doors. You can install and display them. A working CMS is closer to receiving the shop drawings, jigs, tooling, materials list, and controls needed to keep producing matching doors.
The finished pieces have value. They do not give the next crew the same production capability.
What may stop working after a static-file handoff
The answer depends on how the site was built. Do not assume every feature will fail. Do not assume every feature will survive. Test each function against the delivered package.
Lead forms
A static page can display a contact form, but the form still needs somewhere to send and store the submission. That may be a third-party form service, an email handler, a CRM endpoint, or server-side code. If the former agency owns that connection, the form can look normal while leads go nowhere.
Ask for the form endpoint, notification recipients, spam controls, consent language, storage location, retention period, and a complete submission test from the public page to the final inbox or CRM record.
Online booking and CRM connections
Jobber, Housecall Pro, ServiceTitan, and other systems may be connected through scripts, embedded widgets, APIs, or automation tools. The visible booking button may survive inside the HTML. The authorization token or agency-owned automation may not.
Record which company owns each integration account, who can renew credentials, and whether the connection can be recreated without the old platform. Test booking on desktop and mobile before changing DNS.
Call tracking and attribution
Dynamic number insertion can depend on an external script and an active call-tracking account. A static copy may preserve the script tag but lose the account, number pool, routing rules, recording settings, or attribution history. The page still renders. The phone measurement system does not.
Require a list of tracking numbers, the provider, account administrator, porting rights, destination numbers, historical exports, and replacement timing.
Redirects, canonicals, and metadata
A page copy does not always include server-level redirects. If an old service URL redirects to a stronger replacement, that rule may live in a platform setting rather than the HTML. Losing it can turn indexed URLs and backlinks into 404 errors.
Ask for the complete current URL list, status codes, redirect map, canonical tags, title tags, meta descriptions, robots directives, XML sitemap, and structured data. Crawl the old site before the move, then compare the new site URL by URL.
Editing and publishing
Static HTML can be edited, but the workflow may require a developer, code repository, build process, or deployment service. If the contractor expected to add a financing page or update emergency-service hours from an admin screen, the handoff may not support that.
Ask the receiving provider to demonstrate one real edit on a staging URL. Change a paragraph, replace an image, update metadata, publish it, and roll it back. A portable site should survive that test without access to the former agency.
KKS analysis: judge the handoff by restart cost
The useful number is not how many files arrive. It is the cost and time required to restore the same business functions on infrastructure the contractor controls.
A package with 5,000 files can still be incomplete. A smaller, documented package can be enough if the site was intentionally built as a portable static system and includes the source repository, build instructions, deployment configuration, form services, and account access.
We would sort the handoff into three conditions:
- Operational transfer: the receiving provider can host, edit, publish, submit forms, retain tracking, and maintain URLs without rebuilding the site.
- Visual transfer: the pages can be hosted and viewed, but editing, forms, integrations, or measurement need replacement.
- Asset transfer: the contractor receives copy, images, and design materials that reduce rebuild work, but the operating website must be recreated.
None of those labels should be assigned from a contract sentence alone. The receiving provider needs to inspect the actual delivery package.
The 12-part website handoff acceptance test
Use this before final payment, contract expiration, DNS changes, or account removal. Put the answers in a shared document and name the person responsible for each check.
- Domain: confirm the contracting company is the registrant or account holder and can renew, unlock, and transfer the domain. ICANN says registrars must provide instructions for managing and transferring registrations.[5]
- DNS: export current records and verify company-controlled administrator access.
- Hosting: identify the new host, account owner, billing method, backup location, and restore process.
- Files and data: inventory static files, original media, design assets, source files, databases, exports, and documentation.
- Editing: complete one content, image, metadata, and navigation change without the old provider.
- Forms: submit every public form and confirm the lead reaches the correct inbox or CRM with attribution intact.
- Calls: test every displayed and dynamically inserted phone number, including after-hours routing.
- Booking: complete a test appointment on desktop and mobile and confirm it appears in the correct system.
- URLs: crawl the old and new sites. Compare status codes, redirects, canonicals, sitemap entries, and internal links.
- Search access: verify the contractor is a Search Console owner. Google says owners can add and remove users, configure settings, and view all data.[3]
- Analytics: verify a company-controlled user has Administrator access at the right account and property levels. Google requires account-level Administrator access to assign roles and data restrictions.[4]
- Rollback: keep the old site and DNS settings recoverable until the new public site, forms, calls, booking, analytics, and search access pass.
If the current agreement uses Scorpion, send the checklist to the assigned contact and ask which parts are covered by the standard exit package. If another agency is involved, use the same checklist. The technical risk exists wherever the website depends on provider-owned infrastructure.
What to ask Scorpion before signing
- Does “static files” mean a complete browsable copy of every public URL?
- Will the delivery include the source files or build system used to create those pages?
- Which functions depend on Scorpion’s underlying system?
- Will forms, chat, booking, tracking, and call routing operate after the files move?
- Who owns the domain registrar and DNS accounts during the contract?
- Which GA4, Local Services Ads, social, and other accounts will be transferred, and at what permission level?
- Will Scorpion provide the current redirect map, metadata, schema, sitemap, and URL inventory?
- How much transition support is included, for how many days, and at what cost?
- What changes if the customer leaves before the full contract term is complete?
Request written answers in the contract or a signed attachment. The official FAQ is a good starting point, but it cannot describe every customer’s technical setup or negotiated service order.
What to do if you already have a Scorpion website
Do not cancel first. Inventory first.
Start with the 17 contractor website ownership questions. Then have the receiving provider crawl the live site, record forms and tracking, inspect account access, and estimate the restart cost under all three handoff conditions: operational transfer, visual transfer, and asset transfer.
If the files can operate independently, preserve them and move carefully. If the package only preserves the visual pages, plan replacement functions before the cutover. If the handoff is primarily content and creative assets, treat it as a rebuild with reusable material. That is still better than starting empty, but the schedule should reflect the work.
Contractors considering ongoing ownership and portability can also read what a managed contractor website should include.
Not sure what would survive an agency exit? Request a free contractor website audit. KKS will inspect the public site, compare it with one relevant competitor, identify the three highest-priority corrections, and flag the ownership or migration questions that need answers before you cancel or rebuild.
Frequently asked questions
Does Scorpion give customers a WordPress website when they leave?
Scorpion’s public FAQ says customers receive static files, design assets, and content after fulfilling the contract. It also says customers do not own the underlying system.[1] The FAQ does not promise a WordPress installation. Ask Scorpion to state the delivery format and operating requirements in writing.
Can static website files still be useful?
Yes. They may preserve public pages, styling, scripts, images, and other assets. A receiving developer can inspect and host them. Their value depends on whether the package also preserves editing, forms, integrations, tracking, redirects, and deployment instructions.
Is a static website worse than WordPress?
No. A purpose-built static site can be fast and portable. The risk is expectation mismatch. If the contractor bought an editable marketing system, a set of rendered files may require extra work to restore that workflow.
When should a contractor test the handoff?
Before signing, ask for the exact deliverables. Before leaving, test the actual package on staging while the old site and accounts are still available. Do not move DNS until calls, forms, booking, URLs, analytics, and search access pass.
Sources
- Scorpion, Frequently Asked Questions. Accessed August 25, 2026.
- MDN Web Docs, Static site generator. Accessed August 25, 2026.
- Google Search Console Help, Managing owners, users, and permissions. Accessed August 25, 2026.
- Google Analytics Help, Access and data-restriction management. Accessed August 25, 2026.
- ICANN, Registrants' Benefits and Responsibilities. Accessed August 25, 2026.
- WordPress, Tools Export screen. Accessed August 25, 2026.
- WordPress, Backups. Accessed August 25, 2026.