What Happens to a Salesforce Portal When Preparing to Sell the Company?
Portals

What Happens to a Salesforce Portal When Preparing to Sell the Company?

By Troy Amyett•November 15, 2026•7 min read
Speed
AI-narrated

Salesforce portals do not move on their own when ownership changes. They remain attached to the original org, and their future depends on the deal structure, contract language, and the technical plan for the org itself.

What happens to your Salesforce portal during a company sale?

The portal continues to function only if the underlying Salesforce org moves with the business or receives proper access rights in the new structure. In a stock purchase the legal entity usually carries the contract forward, so the sites stay available without immediate consent. In an asset purchase or partial divestiture the sites require explicit approval from Salesforce before any transfer or continued use can occur.

External users keep logging in through the same Experience Cloud sites as long as the org remains active and the licenses stay assigned. Once the org splits or migrates, the sites must be recreated or moved through metadata, and external licenses cannot transfer across org boundaries without new provisioning.

How do contract terms shape what transfers?

Most Salesforce agreements contain assignment restrictions that block automatic transfer without consent. Stock deals often avoid this trigger because the same legal entity continues to hold the contract. Asset deals or carve-outs activate the clause, forcing the buyer and seller to request permission and sometimes accept new terms such as extended commitments or adjusted pricing.

Divestiture language in the original contract can pre-authorize proportional license splits and transition service periods. Without that language the parties must negotiate carve-outs during due diligence. Early review of change-of-control and successor-in-interest clauses gives the seller leverage that disappears after the letter of intent is signed.

Why early contract review prevents last-minute problems

Reviewing the master agreement at least ninety days before close reveals license counts, renewal dates, and consent triggers. The review also surfaces any shelfware that will carry into the new ownership and any restrictions on custom objects that could affect portal functionality after migration.

Sellers who wait until the deal is nearly closed lose the ability to renegotiate protective clauses. Buyers who inherit an org without those clauses face delays while Salesforce reviews the request and potential price resets at renewal. Both sides benefit from documenting the exact sites in scope and confirming that Digital Experiences remain enabled in any target org.

Can you migrate Experience Cloud sites without rebuilding them?

Metadata API migration lets teams move site settings, themes, and page configurations between connected orgs. The process starts by enabling Digital Experiences in the destination org, then retrieving Network, CustomSite, and ExperienceBundle metadata for deployment.

Custom domains can move between production orgs, though the transfer requires a temporary non-HTTPS window and planned downtime. My Domain changes, SSO reconfiguration, and email routing updates must happen in parallel so external users experience minimal interruption. Parallel runs during the cutover window allow teams to validate that case management, knowledge articles, and deal registration continue to work as expected.

What technical steps keep portals usable after the sale?

First inventory every active site, its external user licenses, and all connected integrations. Next decide whether the target is a single consolidated org or separate orgs for regulatory or data-residency reasons. Enable the required features in the destination org and test the metadata deployment in a sandbox.

Reconfigure SSO, update usernames and email addresses, and move any custom domains. Reconcile sharing rules, profiles, and automation so that external users see only the records they should after the cutover. Run sample migrations, full migrations, and delta migrations before the final switch. Coordinate DNS and firewall changes with the hypercare period that follows.

When is consolidating orgs the wrong choice?

Consolidation creates a single customer view but also merges security models, automation, and data ownership. When the acquired business operates under different regulatory requirements or maintains separate partner agreements, keeping separate orgs avoids consent delays and preserves existing external user access patterns. The decision hinges on whether the operational benefit of one org outweighs the added complexity of reconciling two distinct sharing models.

How do you keep the portal running through close and after?

A practical workstream starts with a shared inventory that both legal and technical owners can use. List every Experience Cloud site, its purpose, the profiles and permission sets behind it, the external license types in use, and the integrations that post or read portal data. Include Flow, Apex, and middleware that send email or update records when a portal user acts. This inventory becomes the attachment to the transition plan and the punch list for sandbox testing.

If the deal includes a transition services period, write down who operates the org, who can change sharing or profiles, and how long external users will keep their current login path. Ambiguity here is what usually causes a portal outage after close, not the metadata move itself. Name a single owner for DNS, SSO, and domain cutover, and give external users notice of any username, URL, or login-flow change well before the window.

Confirm whether the buyer will keep Experience Cloud sites, move to a custom portal on the same org, or run both during a transition. The contract and technical plans should describe that end state, because custom domains, SSO, and license mixes change depending on the choice. After the cutover, compare assigned external licenses with actual login and case activity. Rationalization after consolidation can deliver 25–45% savings when sequenced at renewal source. The savings come from removing duplicate licenses and aligning external user counts with actual portal activity rather than from any single technical change. Sequence that review to the renewal date so you are not cutting access in the middle of hypercare.

Frequently asked questions

How long does a typical portal migration take during an acquisition?

Complex consolidations often require ten to twenty weeks when data deduplication, security remodeling, and phased cutovers are included. Simpler migrate-in-place scenarios finish faster once the metadata deployment and domain move are validated.

Do external licenses transfer automatically with the org?

External licenses remain tied to the original org. New licenses must be provisioned in the destination org, and cross-org transfers are not supported. Planning for license counts and user provisioning should begin during due diligence.

What happens to custom domains attached to Experience Cloud sites?

Custom domains can move between production orgs, but the process includes a temporary non-HTTPS setup and scheduled downtime. Teams must update any hard-coded references in integrations and email templates at the same time.

Can legacy Customer or Partner Portals move to a new owner?

Legacy portals continue to function in the original org but receive no new features. Salesforce recommends migrating to Experience Cloud sites before any ownership change so that the modern site metadata can be moved cleanly.

What contingency planning is recommended for surprises during the cutover?

Budgeting at least 30% contingency for surprises is standard advice when inherited technical debt or contract consent delays appear source. Parallel runs and documented rollback steps reduce the impact if issues surface after the cutover completes.

Found this useful? Pass it on.

Share it with someone on your team who's working through the same problem.

Salesforce Custom Portal Template

SF Custom Portal Template

A blank-canvas portal starter kit — customer, vendor, or internal portals. Any object, any use case, your brand.

Troy Amyett

Troy Amyett

Founder & Chief Solutions Architect

9x Salesforce certified. Agentforce Specialist and Agentblazer Legend, 2025–2026. Anthropic-certified in Claude Code and MCP.

Get Insights in your inbox

AI-powered perspectives on Salesforce and Agentforce, delivered weekly.

No spam. Unsubscribe anytime.

Your competitors aren't waiting. Why are you?

Let's talk about what AI agents could do for your business. 30 minutes. No pitch deck. Just answers.

Launch before they do