> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/documentation/cookbook/automatically-move-images-from-lead-record-to-opportunity-on-lead-conversion.md).

# Automatically move images from Lead record to Opportunity on Lead Conversion

This article demonstrates how to automatically move images from a converted lead record to its corresponding opportunity.

## Overview

SharinPix offers a feature to automatically rename albums during the lead conversion process in Salesforce. Renaming an album means associating all images from the converted lead to the newly created opportunity. This ensures that the associated images remain accessible after the conversion.

This feature can be enabled by configuring a custom metadata type in Salesforce.

## Steps to Enable the Feature

**Prerequisites**

* **System Administrator** access is required to modify metadata settings in Salesforce.
* The SharinPix package must be on the latest versions.

**Instructions**

1. Go to **Setup** in Salesforce
2. In the Quick Find box, type **Custom Metadata Types** and select it.
3. Click on **Manage Records** next to the **SharinPix Bypass**.
4. Edit the **LeadConversion** record, tick the **Active** field, and save the record.

Now that the Active field is checked, when a lead is converted, the lead's album contents will be moved to the opportunity's album.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sharinpix.com/documentation/cookbook/automatically-move-images-from-lead-record-to-opportunity-on-lead-conversion.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.