#Sales Cloud157 diskutieren mit

Hello Sean, 

From what I understand, this doesn’t sound like a universally published Salesforce policy where a customer must buy 10 additional UE licenses for an Org Swap. Historically, Org Swaps have generally been handled based on the customer’s existing licensing and commercial agreement, with the replacement org being provisioned to match the appropriate licenses. So if another nonprofit completed an Org Swap in June without this requirement, I’d definitely ask the AE/VP to point to the specific current policy or documentation that requires the additional 10 licenses. It could be a specific provisioning or commercial constraint for this particular account rather than a blanket Salesforce policy, but I’d be interested to hear if others have seen this recently. Hope this helps!

@durgam santhosh

Yes - the native no-Apex route is an Email Alert (the core 'Send Email' Flow action won't render a template's merge fields). Create an Email Alert on Opportunity (Setup > Email Alerts) that uses your Opportunity Lightning template, then call it from your record-triggered Flow as an Action - the alert sets the triggering Opportunity as the Related To, so all your Opportunity merge fields resolve. 

For recipients you can pick Opportunity Owner directly; to send to that custom email field it has to be an Email-type field, then it shows up under Recipient Type 'Email Field'. 

If this helps, please mark it as the Best Answer so it helps the next person - thanks!

Hi Sandeep, 

Good instinct on all four scenarios, here's how I'd draw the line, since this is exactly the kind of decision that determines whether your pipeline reporting stays clean or gets polluted over time. 

The deciding factor should be: is there a commercial transaction to track (revenue movement, approval workflow, quote/contract generation), not just "did the relationship continue." 

Scenario 1 (renews at no additional cost, no change): 

No Opportunity needed. This is a pure Renewal_Cycle__c update: Status__c = Continued. There's no revenue event, no commercial decision-making process for sales to run through, an Opportunity here would be an empty shell with no Amount movement and no real sales motion behind it, exactly the anti-pattern you already flagged wanting to avoid. Just close out the cycle and auto-generate the next Renewal_Cycle__c (or the next Contract term, depending on how your legal team structures true renewals). 

Scenarios 2 & 3 (expansion, upsell, or any revenue change): 

Yes, create an Opportunity, and yes, keep both records with a clear relationship. This is exactly right: 

- Renewal_Cycle__c = the continuation/relationship-level record, tracks CS's forecast and the "will they stay" decision 

- Opportunity = the commercial transaction, tracks the specific upsell/expansion deal, goes through normal pipeline stages, gets its own Amount, Close Date, forecast category 

Add a Lookup field on Opportunity back to Renewal_Cycle__c (Renewal_Cycle__c on Opportunity, not the reverse), this lets you report "which renewal cycles converted into an expansion deal" without forcing every Renewal_Cycle__c to have one. 

Scenario 4 (churn): 

No Opportunity. Status__c = Churned on the Renewal_Cycle__c, done. Some teams create a "Churn" record type Opportunity for pipeline/forecast visibility into lost revenue, that's a judgment call based on whether your leadership wants churned revenue visible in Opportunity-based dashboards specifically, not a technical requirement. 

On your specific question, distinguishing "renewal with no commercial change" from "renewal with expansion" at the point of decision: 

Add a field directly on Renewal_Cycle__c: Renewal_Type__c (picklist: No Change / Expansion / Downsell / Churn), set by the CS rep when they close out the cycle. This becomes your trigger condition: 

- A Record-Triggered Flow on Renewal_Cycle__c (on Status__c or Renewal_Type__c update) checks: if Renewal_Type__c is Expansion or Downsell, auto-create the Opportunity and populate the lookback link. If No Change or Churn, skip Opportunity creation entirely. 

This keeps the decision explicit and auditable (you can report on "how many renewals were flat vs. expansion vs. churn" directly off Renewal_Cycle__c) rather than inferring commercial intent from Opportunity existence alone. 

On linking the final Contract back: once legal generates the new Contract, add a Lookup field on Contract back to the originating Renewal_Cycle__c (or via the Opportunity if one exists), so you get a clean chain: Renewal_Cycle__c > Opportunity (if applicable) > new Contract. This gives full traceability without merging the legal and CS data models. 

This structure scales cleanly to all four scenarios without adding complexity to the ones that don't need it, exactly the outcome you want with no dev on-site.

@Mohanraj S

This is a standard behavior.. unless.. the existing Opportunity already has a product linked to it and Opportunity currency is different. 

Otherwise.. when you convert a Lead to an existing Opportunity (with no product associated).. then Lead Currency will override Opportunity currency. hence, help check your Opportunity situation. 

also refer below link for details