Published July 15, 2026
By Allux Editorial Team
Canceling a financial advisor website provider can take your public site offline, stop forms and integrations, and limit access to content or data. Your domain and customer-owned content may remain yours, while the hosted design, source code, templates, and platform features may not transfer. The outcome depends on your agreement, account ownership, and what you move before the old service ends.
The safe rule is preparation before shutdown: confirm domain control, collect the promised materials, preserve the records your firm needs, prepare the receiving site, and test the cutover before the old service ends.
If you first need to separate the domain, content, design, data, and platform layers, read Do You Own Your Financial Advisor Website?. This guide starts at the next question: what happens when the relationship ends?
Cancellation is not one event
“Cancel” can describe several different actions:
giving notice that a subscription should not renew;
ending a month-to-month plan at the close of the paid period;
requesting immediate cancellation during a refund window;
terminating early while fees remain due;
downgrading to a free or limited plan;
allowing a website, hosting plan, or domain registration to expire; or
losing access after nonpayment, breach, or suspension.
Those events can have different consequences. A website subscription may end while a domain, email account, scheduling tool, analytics property, or other add-on continues. Or several services may stop together because they share the same account.
Before acting, identify the exact service, effective date, notice requirement, remaining fees, export window, and account owner. Your signed order form or service attachment may override a provider’s general public page.
Can you leave a website platform and keep your site?
Sometimes—but “keep the site” is not precise enough.
You may keep the domain and customer-created copy without receiving the hosted implementation that currently makes the site work. You may receive a content export or a static snapshot that still needs a receiving provider, hosting, forms, analytics, and ongoing maintenance. You may retain account access for a limited period, or lose it when the paid term ends.
A content export, a static snapshot, and a runnable website are three different deliverables. The contract should say which one you receive, under what conditions, and for how long.
Use this consequence map before relying on a general ownership statement:
Live website and hosting
What the contract controls: Service end date, access period, handoff support, fees, and exclusions
What the technology controls: Whether the existing site can run outside the provider’s infrastructure
What to secure before cancellation: A tested replacement site and a documented cutover date
Domain, DNS, and email
What the contract controls: Who is entitled to direct or transfer the domain and whether assistance is promised
What the technology controls: Registrar account, transfer lock, nameservers, DNS records, mail records, and recovery access
What to secure before cancellation: Registrar login, registrant details, DNS inventory, renewal status, and email-routing plan
Content, design, and media
What the contract controls: Ownership, license, export scope, format, timing, and permitted reuse
What the technology controls: Whether files can be exported and reconstructed elsewhere
What to secure before cancellation: Delivered copy, original assets, license manifest, page inventory, and explicit exclusions
Forms, leads, and integrations
What the contract controls: Data rights, privacy limits, retention, export fields, and post-term access
What the technology controls: Databases, API connections, webhooks, scheduling, CRM routing, and credentials
What to secure before cancellation: Eligible lead export, integration inventory, receiving endpoints, and test submissions
URLs and search configuration
What the contract controls: Whether URL, redirect, and metadata information is included
What the technology controls: Paths, canonicals, robots rules, sitemap, redirects, server responses, and internal links
What to secure before cancellation: URL map, metadata, known redirects, sitemap, Search Console access, and post-launch monitoring
Records and approvals
What the contract controls: Archive scope, delivery, retention, and responsibility
What the technology controls: Version history, approval logs, screenshots, files, and timestamps actually stored
What to secure before cancellation: Dated copies and evidence your firm and reviewers determine must be retained
What may change after cancellation
The public website may go offline
Some providers take the site offline when the paid website service ends. Others keep the project in the account, move it to a free subdomain, or provide a limited grace period. None of those outcomes should be assumed without checking the current plan and cancellation flow.
Do not cancel the old site because the new homepage “looks ready.” Confirm that every intended page, disclosure, form, download, canonical, and redirect works at the receiving destination.
The domain may continue—but point to the wrong place
A website subscription and a domain registration are separate relationships even when one company sells both. ICANN explains that the registrant enters into an agreement with a registrar and manages the domain through that registrar.
If your firm controls the registrar account, canceling the website does not by itself create a new site. DNS may continue pointing to the provider that is going offline. If the provider holds the domain in its own account, the agreement may require a transfer process and impose a deadline.
Confirm the registrant, registrar login, recovery email, renewal date, transfer status, nameservers, DNS records, and mail records before the service ends. Do not change DNS without knowing what currently handles the website and email.
Content rights may survive while content access ends
Owning copy or customer-supplied images does not guarantee indefinite access to the provider’s editor or files. The contract should identify the delivery method, requested format, deadline, fee, and treatment of provider content and third-party licenses.
Download what you are entitled to receive while the account is active. Record what is missing. If the provider promises assistance after termination, note the request window and who must initiate it.
Forms and integrations can fail quietly
A migrated page can appear complete while its form sends leads nowhere. Calendars, CRM connections, email notifications, analytics tags, cookie controls, downloads, search tools, and compliance-review workflows may rely on the old platform or an account the provider controls.
Inventory each integration, remove secrets from handoff documents, assign the receiving account owner, and submit test data that is clearly marked as a test. Verify the destination of every notification without using real prospect information.
Search visibility can fluctuate
Search rankings are not a file that transfers with the domain. A move can preserve important signals, but the receiving implementation still has to be crawlable and coherent.
Google Search Central recommends testing the destination, mapping old URLs to new ones, implementing redirects, and monitoring both sides of a URL-changing move. Google also notes that ranking fluctuations may occur while the site is recrawled and reindexed.
If the domain and URLs stay the same, preserve the page paths, titles, descriptions, canonical URLs, indexation directives, internal links, and structured data wherever they remain accurate. If URLs change, create a one-to-one redirect map where an equivalent destination exists. Do not redirect every retired page to the homepage.
Your firm’s recordkeeping responsibility does not move automatically
The SEC’s Investment Adviser Marketing Rule small-entity guide states that covered investment advisers must make and keep copies of advertisements they directly or indirectly disseminate.
A website provider does not decide which materials satisfy your firm’s obligations. Before access ends, have the appropriate firm personnel and reviewers determine which website versions, approvals, disclosures, supporting records, and publication dates should be retained. Confirm that the archive is retrievable and usable; do not assume that a platform’s internal history is a complete regulatory record.
What current provider documents say
Checked July 15, 2026. This table summarizes current public documents, not every plan, order form, broker-dealer arrangement, or negotiated agreement. Read the linked source and your governing contract before acting.
FMG’s Terms say service-license rights end at termination. They also describe paid assistance to transfer “Your Content” in a mutually acceptable format, with that duty ending 15 days after termination. If FMG hosts the domain under its third-party account, its stated domain-transfer assistance also ends after 15 days. The applicable order can control term length, notice, and early-termination fees.
WealthReach’s Terms say the Living Site becomes inaccessible at termination while the customer retains domain control. Customer Data has a 90-day retrieval period. A Site Snapshot is available only after a 12-month loyalty period and other stated conditions; the snapshot has significant exclusions and may carry a packaging fee.
Advisor Websites’ Terms say customer-supplied or uploaded content remains the customer’s intellectual property, while the service remains provider property. The public terms require termination notice at least 30 days before the subscription term ends and make invoices scheduled within that window payable. They do not state a general post-termination export format or handoff deadline.
The official Advantage page identifies the advisor website product. Paladin’s general Terms say termination ends service rights and that Paladin may delete personal information or other files. The reviewed public documents do not establish an Advantage-specific portability package.
Squarespace’s cancellation guide says a website can go offline when the subscription ends, while some account panels and content export may remain available. Its domain guide explains that a domain subscription is separate and can remain active, be pointed elsewhere, or be transferred.
The differences are the point. A provider’s public page is evidence, but it is not a substitute for the signed agreement and the actual account configuration.
The pre-cancellation handoff checklist
1. Read the contract clock
Identify the current term, renewal date, notice method, cancellation effective date, and any remaining payment obligation.
Separate cancellation, non-renewal, downgrade, expiration, and termination-for-cause provisions.
Record every export, transfer, or retrieval deadline.
2. Secure account control
Confirm the domain registrant, registrar account, recovery contact, renewal method, transfer lock, and authorization access.
Record nameservers, DNS entries, mail records, and any third-party account the website depends on.
Confirm firm-controlled access to analytics and search properties.
3. Collect the promised materials
Export customer content, original brand assets, eligible media, and any source files or static snapshot the contract includes.
Obtain a page and URL inventory, titles, descriptions, canonicals, indexation settings, sitemap, and known redirects.
Export eligible lead or form data only after the appropriate privacy and security review.
Ask for an asset-license list and explicit statement of non-transferable materials.
4. Preserve the records your firm needs
Save dated copies of the live site and relevant disclosures.
Retrieve available approvals, publication history, and version records.
Have the appropriate firm personnel or reviewers confirm the record set; do not delegate that determination to the website provider.
5. Build and test the receiving destination
Recreate the intended pages, forms, integrations, metadata, and disclosures.
Map each old URL to the same or genuinely equivalent new URL.
Test mobile and desktop pages, navigation, forms, downloads, analytics, consent controls, and account transitions.
Keep the replacement blocked from public indexing only until it is ready to launch, then remove the block.
6. Cut over, verify, then let the old service end
Change DNS only with a rollback record and an identified owner.
Confirm the live site returns the expected status codes, canonicals, robots directives, and sitemap.
Submit test forms and verify notifications and CRM routing.
Monitor Search Console, analytics, server errors, redirects, and important branded queries.
Keep the old service active until the receiving site and handoff package pass acceptance, subject to the notice and termination dates in the governing agreement.
This is a cancellation-readiness checklist, not a complete migration playbook. A separate migration guide should own the full implementation sequence.
How Allux handles cancellation and portability
The section below describes Allux specifically. It is not a claim about every website provider.
The current Allux Terms of Service state that monthly subscriptions are month-to-month and cancel at the end of the current paid billing period; optional annual plans follow the agreed annual term.
After cancellation and payment of any outstanding amounts, Allux provides the portability package automatically or on request. The request window does not expire, and the Terms state that delivery occurs within five business days of cancellation. The package covers the customer content and assets described in the Terms, together with page information, SEO metadata, and the version archive. Allux source code, proprietary platform components, reusable templates, non-transferable third-party licenses, continued hosting, and infrastructure-dependent features are excluded.
The operative scope and conditions are in the Allux Terms of Service and Allux Portability Guarantee. Read both before relying on this summary.
You can also review Allux pricing and plan terms before choosing a plan.