--- schema_version: "1" id: bfc175616246e78c3cb413b1ddb4eac6d6d15bd3185bff3a77724dc48dd3054f title: Merge Memberships collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/merge_membership_merge_action.md canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.merge_membership_merge_action.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: e82b704c5329a57e40524fa5404f9ef4721ec2219bf6ebc94dd13ed48a9f0884 description: Use the Merge Loyalty Program Memberships action in Flow Builder to merge a source membership and a target membership. After the merge is completed, the status of the source membership changes to Merged while the status of the target membership remains active. products: - Loyalty Management release: "264" --- # Merge Memberships Use the Merge Loyalty Program Memberships action in Flow Builder to merge a source membership and a target membership. After the merge is completed, the status of the source membership changes to Merged while the status of the target membership remains active. ### Required Editions
Available in: Lightning Experience in Enterprise, Performance, Developer, and Unlimited Editions that have Loyalty Management enabled
By default, all the transaction journals and points of the source membership are transferred to the target membership. If you want, you can: - Transfer the vouchers of the source membership to the target membership. - Assign the higher current tier between the source and target memberships to the target membership. When traceability is enabled, you can’t merge members when the source member has pending traceability records. To learn how to process pending trace records, see [Set Up Traceability](https://help.salesforce.com/s/articleView?id=xcloud.loyalty_async_processing_trace_redemption.htm&release=264.0.0&type=5 "To link redemption transactions directly to source accrual transactions, turn on traceability for redeemable currencies. Set up Data Processing Engine definitions and invocable actions to process trace records and expire points."). To merge memberships, provide these inputs to the action: | Input | Description | | --- | --- | | Reason | Enter the reason for merging the memberships. | | Source Loyalty Program Member ID | Enter the ID of the Loyalty Program Member record that moves to the Merged status and whose points and vouchers are transferred to the target membership. | | Target Loyalty Program Member ID | Enter the ID of the Loyalty Program Member record that remains active after the merge and gets the points and vouchers transferred from the source membership. | | Transfer Vouchers to Target Member | Select whether to transfer the vouchers of the source membership to the target membership. | | Use Higher Current Tier for Target Member | Select whether to assign the higher current tier between the source and target memberships to the target membership. | ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-loyalty_management-264-0-0-production-enus/0590ce3e-5a09-45ab-8e5e-68f359c35886/images/icon_tip.png) Tip You can use resources in the action to populate the values for the action inputs from either the preceding elements in the flow or from external systems. After the action merges the memberships, a Loyalty Program Member Merge record is created and the status of the record is set to Merged. The Loyalty Program Member Merge record stores the details of the transaction journals and vouchers that are transferred from the source membership to the target membership. ![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-loyalty_management-264-0-0-production-enus/0590ce3e-5a09-45ab-8e5e-68f359c35886/images/icon_example.png) Example Maria Jimenez has two memberships, Maria J and M Jimenez. Maria wants to keep Maria J as the active membership and transfer the points and vouchers of the M Jimenez membership to the Maria J membership. Here’s what both memberships look like: | Loyalty Program Member | Points Balance | Count of Vouchers | Current Tier | | --- | --- | --- | --- | | Maria J | 200 | 1 | Silver | | M Jimenez | 800 | 4 | Gold | To merge Maria’s memberships, these values are provided as the inputs for the Merge Loyalty Program Memberships action: - Reason: Member request - Source Loyalty Program Member ID: 0lMT100000001JnMAK - Target Loyalty Program Member ID: 0lMT100000001JnMAI - Transfer Vouchers to Target Member: Included - Use Higher Current Tier for Target Member: Included After the memberships are merged, here’s how the Maria J membership looks: | Loyalty Program Member | Points Balance | Count of Vouchers | Current Tier | | --- | --- | --- | --- | | Maria J | 800 | 5 | Gold | #### See Also - [_Salesforce Help_: Understanding How Merging and Unmerging Memberships Work](https://help.salesforce.com/s/articleView?id=xcloud.merge_membership_workflow.htm&release=264.0.0&type=5 "Learn how merging and unmerging memberships work.") - [_Salesforce Help_: Points to Consider Before Merging or Unmerging Memberships](https://help.salesforce.com/s/articleView?id=xcloud.merge_membership_considerations.htm&release=264.0.0&type=5 "Loyalty Program Member records can be merged and unmerged only when the records match a set of predefined conditions. Review the conditions before you use actions in Flow Builder to automate membership merging and unmerging.") - [_SOAP API Developer Guide_: Core Data Types Used in API Calls](https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_calls_concepts_core_data_objects.htm)