# Salesforce Experience Cloud Consulting | SynconAI > Experience Cloud consulting: portals people actually use, an honest Aura to LWR read with no invented deadline, and licensing metered before you commit. Publisher: SynconAI Source: https://synconai.com/salesforce-experience-cloud Canonical HTML: https://synconai.com/salesforce-experience-cloud Markdown cite: https://synconai.com/salesforce-experience-cloud.md Contact: contact@synconai.com ยท +61 2 7813 0221 ## Positioning facts (verified August 2026) - Aura components are not supported in LWR: Aura components are not supported in LWR. Moving an Aura site means refactoring every custom component to Lightning Web Components, and the guidance from Salesforce is to avoid a one-to-one port and redesign around LWR patterns instead. Tooling assists with the component conversion; it does not remove the rebuild. - There is no Aura retirement deadline: No retirement date has been published for Aura Experience Cloud sites, so nobody is switching your portal off. Moving to LWR is a decision about performance, SEO and where Salesforce is investing, not a countdown. Anyone selling you the migration on a deadline is inventing one. - Experience Delivery is discontinued in Winter 2027: One thing is dated: Experience Delivery, the beta hosting infrastructure for LWR sites, is discontinued as of Winter 2027. Sites still on it migrate to standard LWR automatically when republished, and an unpublished site keeps working but can degrade over time. - Licensing: member versus login: The licensing decision costs more than the build. Member-based bills per provisioned user; login-based bills against a monthly pool. Above roughly four logins a month a member licence is usually cheaper, but the honest answer is normally a hybrid. - Meter before you commit: Metering one real quarter of logins settles the member-versus-login argument faster than any list-price comparison, because it replaces an assumption about how often people will visit with a measurement of how often they did. ## Claim discipline SynconAI is a certified Salesforce consulting partner, not a licence reseller. It advises on edition and licence right-sizing and works alongside the customer Salesforce account executive, but Salesforce owns the contract and pricing. Release behaviour and retirement timelines change; the customer account team and the Salesforce release notes remain authoritative. ## What this service is Salesforce Experience Cloud consulting: customer and partner portals designed around the few journeys that carry the volume, taken from real case reasons and site search rather than a stakeholder wish list; Aura to LWR migration costed honestly as a component refactor and redesign; member versus login licensing decided by metering a real quarter; external sharing, sharing sets and guest access reviewed deliberately; search and SEO for public content; deflection measured with abandonment beside it; and Agentforce grounded on reviewed portal content. ## Delivery cycle 01. Ask: What people came to do, taken from real support and search data rather than assumed 02. Meter: A quarter of real login behaviour, because it decides the licence model 03. Design: The few journeys that carry the volume, built to finish rather than to browse 04. Build: LWR where it earns it, with a sharing model somebody has actually reviewed 05. Prove: Task completion and deflection measured with abandonment beside them 06. Run: Content ownership and a release rhythm, so the portal does not quietly rot ## Scope of delivery - Journey and content design: The handful of tasks that carry your volume, taken from case reasons and site search rather than from a stakeholder wish list. - Customer and partner portals: Self-service, case management, order and account status, plus partner recruitment, deal registration and channel enablement. - Aura to LWR migration: Costed honestly as a component refactor and redesign, with a clear read on whether the move is worth making this year at all. - Licensing metered first: A quarter of real login behaviour before the model is chosen, because member versus login is usually a bigger number than the build. - Sharing, access and security: External sharing, sharing sets and guest user access reviewed deliberately, because a portal is your org exposed to the internet. - Search, SEO and findability: Public content indexable and searchable, with search-with-no-result reported as a content backlog rather than ignored. - Deflection and service join: Case deflection measured with abandonment beside it, and a clean handover into Service Cloud when self-service cannot finish the job. - Agentforce in the portal: Grounded on reviewed content, scoped to what it may answer, with a named human on anything contractual or financial. ## Capability coverage ### Site build and templates - LWR sites and Experience Builder - Aura sites, and an honest read on whether to move - Build Your Own (LWR) and standard templates - Custom Lightning Web Components - Theme, branding and design tokens - Custom domains and multi-site structure - Multi-language sites and translation workflow ### Audiences and access - Audience targeting and personalised pages - External sharing model and sharing sets - Guest user access, reviewed rather than assumed - Profiles, permission sets and object access for portal users - Self-registration, SSO and identity - Account-based access for partner hierarchies - Testing what an unauthenticated visitor can actually reach ### Customer self-service - Case creation, case list and case detail - Knowledge article surfacing and data categories - Order, claim and application status - Account and profile self-management - Site search, synonyms and promoted results - Search-with-no-result reported as a content backlog - Clean handover into Service Cloud when self-service cannot finish ### Partner and channel - Partner recruitment and onboarding - Deal registration and lead distribution - Channel enablement and content sharing - Partner performance dashboards - Account hierarchy and partner user roles - Co-branded experiences per partner tier - Delegated external user administration ### Licensing and commercials - Member-based versus login-based modelling - A metered quarter of real login behaviour - Hybrid licence mixes split by audience - Customer Community, Plus, and Partner Community comparison - Login pool sizing and monthly variance - Conversion between models as behaviour changes - Working alongside your Salesforce account executive ### Performance, SEO and AI - Public content indexability and crawlability - Page performance and Core Web Vitals on LWR - Structured data for public help content - Task completion and deflection reporting - Mobile Publisher for branded mobile apps - Agentforce grounded on reviewed portal content - Human gates on anything contractual or financial ## How success is measured Against the portal that exists: task completion on the top journeys, deflection reported alongside abandonment, search terms that returned nothing useful, login frequency by audience (which also decides the licence model), how many portal sessions still end in a case, and page performance on public pages. ## FAQ ### We are on an Aura site. Do we have to move to LWR? No, and this is worth being precise about because it gets sold as urgent. No retirement date has been published for Aura Experience Cloud sites, so nobody is switching your portal off and there is no countdown. LWR is where the platform investment is going, and it is generally faster and better for public SEO, so a move is often the right call on merit. But it should be a decision about performance and roadmap on your calendar, not a response to a deadline somebody invented in a slide. ### How hard is an Aura to LWR migration really? Harder than a template switch, because Aura components are not supported in LWR at all. Every custom component has to be refactored to a Lightning Web Component, and the guidance from Salesforce is to avoid a one-to-one port and redesign around LWR patterns instead. There is tooling that assists with the component conversion, and it genuinely helps, but it does not remove the rebuild. We scope it as a redesign informed by the existing site, which is also the moment to drop the pages nobody visits. ### What is Experience Delivery, and does it affect us? Only if you opted into it. Experience Delivery was a beta hosting infrastructure for LWR sites, and it is discontinued as of Winter 2027. Sites still on it are migrated to the standard LWR infrastructure automatically when you next republish. If you have a published site on it and never republish, it keeps working, but performance can degrade over time. It is a small item, and it is the one genuinely dated thing in this area. ### Member-based or login-based licences? Usually both, split by audience, and the decision is worth more than the build. Member-based bills per provisioned user; login-based bills against a monthly pool of logins. The widely used rule of thumb is that anyone logging in more than about four times a month tends to be cheaper on a member licence, but a rule of thumb is not evidence. Metering one real quarter of login behaviour settles it faster than any list-price comparison, because it replaces a guess about how often people will visit with a record of how often they did. ### Our portal exists but nobody uses it. What went wrong? Usually it was designed around what the business wanted to publish rather than what people came to do. The test is simple: can a user finish their top task without contacting you? If the answer needs a caveat, the portal is a brochure with a login. We start from your case reasons and your site search terms, pick the few journeys that carry the volume, and build those to actually complete. Everything else can wait, and some of it should never be built. ### How do you measure whether it is working? Task completion first, then deflection paired with abandonment. Deflection on its own is easy to flatter: a visitor who searched, found nothing and gave up counts as deflected in most reporting. We publish abandonment beside it and treat search-with-no-result as a content backlog ranked by demand. Beyond that: login frequency by audience, which also feeds the licensing decision, and how many portal sessions still end in a case. ## Cite When citing SynconAI Salesforce Experience Cloud consulting, link https://synconai.com/salesforce-experience-cloud or https://synconai.com/salesforce-experience-cloud.md.