Category: Admin how-to

  • How to clone a record with its related records in Salesforce

    How to clone a record with its related records in Salesforce

    The short answer: To clone a record with related records in Salesforce, use the Clone with Related action. Salesforce Help documents it for Opportunities (contact roles, products and product schedules) and Campaigns, in Lightning Experience only. For other objects, build a Flow that copies the children. Either way, reset the dates, stage, owner and unique fields on the copy, because Clone copies what’s there.

    The renewal rep wants last year’s Opportunity: same products, same contact roles, none of the old notes. She finds Clone, clicks it, and gets a record. The Close Date says March. The Stage says Closed Won. The products didn’t come, so she re-adds nine of them by hand and forgets the tenth.

    Nothing is broken. Clone did what it was built to do. The trouble is that “a copy” and “a new deal” are different things, and the gap between them is where the stale data comes from.

    What does the standard Clone button copy?

    It copies field values from the record you are on into a new record, and only the fields that record page shows. Salesforce Help says which fields are copied depends on how the record page is configured: with the Record Detail component, fields come from the page layout, and with Dynamic Forms, from the field sections on the original page.

    Help lists what comes out blank:

    • Fields you don’t have access to.
    • Fields you have only read-only access to on the record you’re cloning.

    It also says you need Create on the object and Read on the record. Clone itself is available in Lightning, Classic and the mobile app, per the Opportunity considerations article, but related records are a separate step.

    One audit-field quirk: per a Salesforce knowledge article, a user with the Set Audit Fields upon Record Creation permission can end up with the original record’s Created Date on the clone in Lightning.

    Does Salesforce have Clone with Related, and for which objects?

    Yes, for some objects. Salesforce Help documents Clone with Related for Opportunities and Campaigns. The Spring ’20 release brought it to Opportunities: Salesforce’s blog says cloning an opportunity now lets you also copy contact roles, products or product (line item) schedules.

    The details worth knowing, all from Salesforce Help:

    • It is Lightning Experience only, and it isn’t available in the Salesforce mobile app. Editions: Professional, Enterprise, Performance, Unlimited and Developer.
    • The admin adds the action to the page layout, as the Spring ’20 post describes for Opportunities.
    • You can include up to 999 related records in total, cloned in batches of 200. Validation rules, Apex triggers and workflow run separately for each batch.
    • For campaigns, you can clone related records such as campaign member statuses and, if you use Account Engagement, some of its assets. Some fields change or come out blank in the copy, such as the new campaign and asset IDs.
    • A related record with a custom field that must be unique needs that value deleted before you clone it.

    Help’s general Clone Records article doesn’t list every object that offers Clone with Related, and the product clone article describes copying a product with its price book entries rather than a related-records picker. If your object isn’t in the documented list, check the actions available for it in Object Manager before you assume it exists.

    How do you clone related records with a Flow?

    Build a screen Flow that creates the new parent, then loops through each type of child and creates copies pointed at the new parent. A write-up from Salesforce Time, a community blog, builds exactly this for Cases: a screen to adjust a few fields, checkboxes for which children to copy, then Get Records, Loop, Assignment and Create Records for each child type.

    The shape, in plain steps:

    1. Pass the record in as an input variable, so a quick action can launch the Flow.
    2. Show a screen with the fields people may change, defaulted to the current values.
    3. Create the new parent from only the fields you map. Anything you don’t map isn’t copied, which is how you leave out the Id and the fields that shouldn’t travel.
    4. For each child type, use Get Records to fetch all matches, loop through them, set the parent lookup to the new parent’s Id, and add each to a collection.
    5. After the loop, create the whole collection in one Create Records element, not one record at a time inside the loop.
    6. Add the Flow to the page as a quick action.

    A record-triggered Flow can also do the copying, but as the same article notes, it can’t show a screen, so the user can’t choose which children to copy. The child types must be decided in advance.

    The cost shows up later, and I’d call it the real price of this approach. Each object gets its own Flow. Each child type is another branch. A new field added to the object next quarter is silently left off the copy until someone remembers to add it to the Flow. If you build one, write down which fields it maps and which it deliberately skips. Flow’s own version history won’t remember your intent for you either, and we plan a post on Flow edit history for tidying them.

    What goes wrong when you clone, and what should you reset?

    Most clone problems come from carrying forward something that was true for the original and isn’t true for the copy. Reset these on the way, whether by Flow, by training or by rule.

    FieldWhy it goes staleReset to
    NameTwo records called the same thingAdd the year, “Renewal” or the cycle
    Close Date or any “due” dateThe copy keeps last cycle’s date, so it looks overdue or already wonA real future date, or blank
    Stage or StatusA copy of a Closed Won deal is a Closed Won dealThe first stage of the process
    Probability, Forecast CategoryUsually follows stage, but not alwaysCheck that it follows the new stage
    OwnerMight not be the person who will work itThe person who will work it
    Amount, quantity, priceLast year’s price is not this year’sRe-check against the current price book
    Description, next steps, notesOld conversation, sometimes about a different yearBlank, or a fresh template
    Type (New versus Renewal)A renewal still labeled New distorts reportsRenewal, if that’s what it is
    Contract numbers, external IDs, integration IDsA unique value on two records fails on save, or worse, syncs as a duplicateBlank, or generate a new one
    Approval status, signed flags, document linksLooks approved when nobody approved itNot submitted, unchecked, blank

    Two more traps. First, fields not on the page layout may not come along, and read-only fields come out blank, so a copy can be missing values that nobody reset on purpose. Second, a clone runs your validation rules and triggers like any other create, so a required field that the original filled in another way can block the save. That is annoying and also correct.

    What to do Monday:

    1. Pick the object your team clones most and write down which fields need resetting, using the table above.

    2. Open its page layout and check whether Clone with Related is there. If you clone Opportunities and it isn’t, add it, then test with a record that has products and contact roles.

    3. If there is already a clone Flow, list what it maps and what it skips, and add any field created since it was built.

    4. Ask three reps how they really clone. The answers will differ.

    Where we come in

    Sistership, by GTM Cloud, is in early access. It is a second way to clone: rules blank, set or protect fields on the copy, you choose which related records come along, and a log shows what changed. The standard Clone button stays as it is, so decide which one your layouts offer. There’s no undo, because a clone is a new record: delete the copy. See the Sistership page.

    Questions people ask

    Does the Salesforce Clone button copy related records?

    No. The standard Clone button copies field values to a new record, not its children. For Opportunities and Campaigns, Salesforce Help documents a separate Clone with Related action that lets you pick related records to copy. Everything else needs a Flow or custom code to bring children along.

    Why does my cloned record have the old close date or stage?

    Because Clone copies the values it finds. Salesforce Help says fields are copied according to the page layout or form on the original record, so nothing resets the date or stage for you. You need to change them by hand, in a Flow, or with rules that run when the copy is created.

    Is Clone with Related available in the Salesforce mobile app?

    No. Salesforce Help says Clone with Related isn’t available in the Salesforce mobile app, and the Opportunity article says it is in Lightning Experience only. The plain Clone action is available in mobile. If reps clone from their phones, plan for the difference.

    Sources

  • Salesforce field history tracking: the limits, and what to do about them

    Salesforce field history tracking: the limits, and what to do about them

    The short answer: The Salesforce field history tracking limit is 20 fields per object, and the history stays in the UI for about 18 months (24 months through the API). Tasks and Events get six fields. Field Audit Trail, Salesforce’s own add-on, raises the cap to 200 fields per object and keeps history until you delete it. Otherwise you choose your 20 carefully.

    A VP forwards a screenshot with one line: “What was this amount last quarter, and who changed it?” You open the record, find the history list, and see a tidy table that starts three weeks ago. Or nothing at all, because Amount was field number 21 and nobody picked it.

    Field history tracking is a good feature with hard edges. Knowing the edges before the question arrives is the difference between a two-minute answer and an afternoon of asking people what they remember.

    How many fields can Salesforce field history track?

    Twenty per object is the standard limit, as reported by Salesforce Ben, and it applies to standard and custom objects alike. Events and Tasks are tighter: Salesforce Help says you can track up to six fields per object on them, and only standard fields qualify.

    The User object has its own arrangement. Salesforce Help says admins can track a maximum of 20 fields there, chosen from a fixed list that includes Name, Email, Profile and Role. Winter ’27 brought field history to the User object, and we cover it in field history tracking for the User object.

    Two more edges from the same Help article. Long text fields with more than 255 characters are logged only as an edit: the before and after values aren’t stored or shown. And as reported by Salesforce Ben, formula fields can’t be tracked at all.

    How long does Salesforce keep field history?

    About 18 months in the UI and up to 24 months through the API, per Salesforce Help. Data older than 18 months can be retrieved with Data Loader or the queryAll() API. Salesforce Ben reports the same split.

    The upside is that field history doesn’t count against your data storage, according to the same Help article. The downside is the clock. A question about a change two years ago has no native answer unless you did something about it two years ago.

    What is Field Audit Trail?

    Field Audit Trail is Salesforce’s own extension to field history tracking, sold as an add-on. Salesforce’s Trailhead module says it lets you track up to 200 fields per object, with custom retention periods in months or years and history that can be stored indefinitely. Salesforce’s Shield product page says up to 10 years. Salesforce Help says that with Field Audit Trail turned on, Salesforce retains history until you manually delete it. The sources describe the retention a little differently, so read your own contract and the current documentation before you promise an auditor a number.

    Some older articles still say Field Audit Trail raises the limit to 60 fields. That figure appears in Salesforce Ben’s guide, but Salesforce’s current Trailhead and Shield pages say 200. Trust the Salesforce pages.

    If you need long, defensible retention on a set of regulated fields, this is the native answer and it deserves a real look. Check which editions and licenses it is available for in your org.

    How do you choose which 20 fields to track?

    Track the fields where a change tells a story and where someone will one day ask “who did that?”. Start there, not with the fields that are merely important.

    A short method that works:

    1. List the disputes you have already had. Amount, Close Date, Stage, Owner, Account Type, Status on Cases. Real arguments beat guesses.
    2. List the fields that drive money or access. Forecast category, discount, contract end date, a credit-hold checkbox.
    3. Skip fields that change on every save. Anything updated by automation all day will fill the history list with noise and make the real change harder to find.
    4. Skip what history can’t show. Formula fields and long text over 255 characters won’t give you useful values.
    5. Leave two or three slots empty. The next question will be about a field nobody thought of.

    Then turn it on. Per Salesforce Ben, for a standard object open it in Object Manager, go to Fields & Relationships and choose Set History Tracking. For a custom object, enable Track Field History in the object’s details first, then pick fields. Ben also reports that since Summer ’24 there is a dedicated Field History Tracking page in Setup that manages objects and fields together. Changes are tracked from the moment you select a field, but users see them only after you add the history related list to the page layout or record page.

    That last point catches people. Tracking starts when you save the selection, never earlier. There is no back-filling.

    What do you do when 20 fields is not enough?

    You have four honest options, and the right one depends on how long you need the history and how many objects are involved.

    OptionGood forWatch out for
    Choose better fieldsMost orgs. Often the limit is a prioritization problemYou will still have nothing for field 21
    Field Audit TrailRegulated fields, long retention, one vendorSold separately, so check your edition and contract
    Your own history object, fed by a Flow or triggerSmall, specific needs on one or two objectsYou build it, you maintain it, and its records count against your data storage
    A history app that keeps its own logMany fields or objects, retention you set, restore from the logAnother thing to install and secure; history starts when you begin

    A custom history object is the one admins try first, and it works. It is also the one that turns into a Flow nobody dares touch in two years. If you go that way, write down which fields it covers.

    Whatever you choose, remember native history is a log of field changes, and nothing more. It doesn’t tell you who changed a permission or a setting. For that you need other audit tools, and we get into that in the User object post.

    What to do Monday:

    1. Pick your five most-argued-about objects and write down which fields each already tracks.

    2. For any object at 20 fields, review the list and swap out fields that change by automation.

    3. Check the page layout. History that nobody can see is history nobody uses. Add the related list where it’s missing.

    4. Ask the person who owns audits what retention they need, in years. That number decides whether you need more than native.

    Where we come in

    Wake, by GTM Cloud, is in early access. It logs changes to the fields and objects you choose, past the native 20-field limit, with retention you set. It sits beside Salesforce’s own history, so you don’t turn anything off. It stores history in Big Objects in your org, starts from the day you begin monitoring a field, and doesn’t back-fill. See the Wake page.

    Questions people ask

    What is the field history tracking limit in Salesforce?

    Twenty fields per object for standard and custom objects, as reported by Salesforce Ben. Per Salesforce Help, Tasks and Events allow six, standard fields only. Field Audit Trail, an add-on, raises the limit to 200 fields per object. Check your edition, because availability depends on it.

    How far back does Salesforce field history go?

    Native history is kept for about 18 months in the UI and up to 24 months through the API, according to Salesforce Help. With Field Audit Trail turned on, Salesforce retains history until you delete it. Tracking starts when you select a field, so you can’t recover changes made before that.

    Does field history count against Salesforce storage?

    No. Salesforce Help says field history data doesn’t count against storage limits. That changes if you build your own history object, because its records use data storage like any other custom object. It is one more reason to compare options before you build a log with a Flow.

    Sources

  • How to run a user access review in Salesforce

    How to run a user access review in Salesforce

    The short answer: A Salesforce user access review is a scheduled check that every active user’s access still matches their job, with a named person’s decision recorded. You can run one by hand: list active users, open each one’s access summary, query who holds the high-risk permissions, record keep or remove, and save the export. Do it at least yearly, and quarterly for the riskiest permissions.

    Say a contractor’s agreement ended in June. In November, someone notices the user is still active, still on a permission set called “Temp”, and still able to export reports. Nobody did anything wrong in the moment. Access doesn’t expire by itself, and nobody was assigned to look.

    That’s what a review is for. It’s an unglamorous job, and the manual version is more doable than the dread suggests.

    What is a user access review, and why do auditors ask for one?

    It’s a periodic check, owned by a person with authority, that each user’s access is still appropriate, plus a record of what was decided. Auditors ask because access piles up quietly: people change roles, contracts end, and nobody removes what is no longer needed.

    As reported by Security Boulevard, its SOC 2 guidance is to review user access at least annually, with quarterly reviews recommended, and to keep logs of each review and of how any problems were resolved. The same article tells readers to confirm the exact expectations with their auditor, which is good advice. Your auditor sets the frequency and the evidence format, so ask before you design the process.

    What should the review cover?

    Cover every active user, plus the other things that can act like one. That means:

    • Active users: their profile, role, and the permission sets and permission set groups assigned.
    • Integration users, which usually hold broad access and rarely get reviewed.
    • Any agent user, if you run AI agents. Our post on telling what an AI agent changed explains why the agent’s user matters.
    • Public groups and queues, which grant record access that isn’t visible on the permission screens.
    • Users who haven’t logged in for a long time but are still active.

    One housekeeping note: permissions on profiles aren’t going away on a fixed date. As reported by Salesforce Ben in July 2026, Salesforce updated its knowledge article to say the planned retirement was cancelled, while still recommending a permission-set-led model. So you’ll be reviewing both profiles and permission sets for a while.

    How do you run a user access review with native tools?

    Use five steps. Each uses something already in Setup or the query editor.

    1. Export the active users. A report or list view with name, username, profile, role, active flag and last login. This is your population, and you’ll attach it to the evidence file.
    2. Open a user’s access summary. In Setup, search Users, open a user and choose View Summary. As reported by Salesforce Ben, it arrived in Summer ’24 and shows object and field permissions, user permissions, public group and queue membership and custom permissions on separate tabs. Do this for a sample, or for everyone with broad access.
    3. Open the permission sets they hold. View Summary on a permission set shows its object, field and custom permissions and the permission set groups it belongs to. Salesforce Ben described this summary as beta at the time and heading for general availability, so check what your org shows.
    4. Query who holds the high-risk permissions. In the Developer Console query editor or your preferred client, run the query below. Swap the permission field for each one on your list.
    5. Record a decision for each person. Keep, change or remove, with the reviewer’s name and the date. Then make the changes and note when you did.
    SELECT Assignee.Name, Assignee.Username, PermissionSet.Label, PermissionSet.Profile.Name
    FROM PermissionSetAssignment
    WHERE Assignee.IsActive = true
    AND PermissionSet.PermissionsModifyAllData = true

    As we understand the data model, every profile has a permission set behind it, so don’t filter those out. Check that your results include a known administrator before you trust the query. Users who get a permission through a profile should appear alongside those who get it through a permission set.

    For a single field, there is a newer option. As reported by salesforcebreak, a Field Access Summary in Object Manager shows one field’s access across profiles, permission sets and permission set groups. That source described it as in preview in Summer ’26, not generally available, so treat it as a bonus.

    Which permissions should you check first?

    Start with the ones that bypass the sharing model or move data out. This is our short list, from practice, not an official Salesforce one. As reported by Salesforce Ben, its least-privilege guidance flags Modify All Data, API access and report exports among high-risk permissions to monitor.

    PermissionWhy it goes firstQuery field
    Modify All DataRead, edit and delete every record, whatever sharing saysPermissionsModifyAllData
    View All DataRead every record, whatever sharing saysPermissionsViewAllData
    Export ReportsSends report data out of SalesforcePermissionsExportReport
    Manage UsersCan create users and change what others can doPermissionsManageUsers
    API EnabledOpens the door to data loaders and integrationsPermissionsApiEnabled

    API Enabled is the one that trips people up. Integration users need it, but a sales rep who has it can pull data through tools you never see. Ask for every holder to have a reason you can write in one line.

    How often should you run a user access review?

    Run a full review at least once a year and a short one every quarter, covering only the five permissions above. That follows the pattern Security Boulevard reports, though your auditor has the final say.

    Add triggers on top of the calendar. Review someone’s access when their role changes, when a contract ends, and when an acquisition or reorganization moves people around. Those events are where access piles up, so don’t wait for the next quarter.

    What evidence should you keep?

    Keep enough that someone who wasn’t there can follow what happened. For each review:

    • The exported user list, dated.
    • The query results for each high-risk permission, dated.
    • Each decision, with the reviewer and the date.
    • A note of every change made and when.
    • A Setup Audit Trail export covering the period.

    On that last item: as reported by Salesforce Ben, Setup Audit Trail shows the last 20 changes on screen and a CSV download covers the last 180 days. It records permission and profile changes with the user who made them, so it’s your proof that the removals happened. Save the file, because it won’t keep it for you. Also as reported, Winter ’27 moves access to the trail behind a dedicated View Setup Audit Trail permission, as a release update that preserves existing access. We’ll cover it in a separate post.

    User Access Policies can automate granting and removing access, but as reported by Salesforce Ben, their Recent User Access Changes view shows only changes from policies still in effect. It isn’t a complete history, so don’t treat it as evidence.

    What to do Monday:

    – Run the query above for Modify All Data and write down every name.

    – Next to each name, write one line saying why they need it. Where you can’t, flag it.

    – Export the active user list and the Setup Audit Trail, and save both in a dated folder.

    – Ask your auditor how often they expect a review, and what format they want.

    Where we come in

    Watchbill, by GTM Cloud, is pre-release and isn’t publicly listed yet. It shows every permission with what grants it, answers who can do a thing, compares users and permission sets, keeps snapshots and a change history, and runs a review campaign that managers finish and that closes with a sign-off. Version 1 only reads access and changes none. See the Watchbill page, or ask our Salesforce services team to work through an audit with you.

    Questions people ask

    How do I find everyone with Modify All Data in Salesforce?

    Query PermissionSetAssignment for active users where the permission set’s PermissionsModifyAllData is true, as in the example above. Profiles are included because each has a permission set behind it. Check that a known administrator appears in the results, then compare the count against what you expected.

    Does Salesforce have a built-in access review?

    We didn’t find a native review-and-sign-off workflow in the sources we read. The native tools show access: View Summary, permission set summaries and queries. A manager’s decision and the evidence of it still need a document or spreadsheet that you keep yourself.

    How long should I keep access review records?

    Ask your auditor. Retention periods come from your compliance framework and your contracts, not from Salesforce. Keep the records somewhere the audit team can reach, with the dates visible, and plan to keep the export files even after the org’s own logs have rolled off.

    Sources

  • Can you undo a lead conversion in Salesforce?

    Can you undo a lead conversion in Salesforce?

    The short answer: No. Salesforce’s own Help says “You can’t reverse a lead conversion.” The Lead stays in your org as a converted record, and the Account, Contact and Opportunity it created stay too. Your options are to fix those records by hand, delete them and rebuild the Lead, or restore from a backup. The better move is to stop the bad conversion first.

    Say a rep converts a Lead on Friday afternoon. The company was already a customer, but nobody ticked “existing account”, so Salesforce made a second Account with a new Contact and an Opportunity nobody asked for. On Monday you find all three, and the Lead you’d like to get back is flagged as converted.

    There is no Unconvert button. Here is what you can do, what each choice costs, and where to put your effort so it doesn’t happen again.

    Is there a native way to unconvert a lead?

    Not according to Salesforce. The Help article for converting qualified leads states that you can’t reverse a lead conversion, and its documentation offers no supported route back that we could find. Converted Leads are not deleted either: the record remains, and per the same article it stops appearing in search unless your admin has given you the View and Edit Converted Leads permission.

    That leaves you with records on both sides of the fence. The converted Lead points at the new Account, Contact and (if created) Opportunity. Activities, notes and anything else the rep did before conversion now sit on the Contact or Opportunity, not on a live Lead.

    What do people do when a conversion goes wrong?

    You have three practical choices, and each one costs something. None is documented by Salesforce as an undo, so treat them as practitioner workarounds, and try them in a sandbox first.

    WorkaroundWhat it involvesWhat it costs
    Fix forwardLeave the records, then edit them: re-parent the Contact to the right Account, rename or merge the Account, delete the OpportunityFastest. The Lead stays converted, so any process that expects it to be a live Lead (a nurture program, a queue) won’t pick it up again
    Delete and rebuildDelete the Account, Contact and Opportunity the conversion created, then create a new Lead with the old valuesYou re-key data from memory or a report. Activity history and anything related to the deleted records goes with them
    Restore from a backupUse an export or a backup tool to put the original Lead backOnly works if you took the backup before the conversion. Re-linking the activities is still your job

    “Fix forward” is what most teams settle on, and it’s often the right call. If the damage is a duplicate Account, the merge is the repair. We cover that in how to merge duplicate accounts in Salesforce.

    The one to be careful with is “delete and rebuild”. Deleting the Contact deletes the trail you were trying to protect. If anyone has worked the new records since Friday, you are deleting their work as well.

    What does conversion actually do to your data?

    Conversion is the hand-off in the Convert stage of the lead-to-renewal path. It creates an Account, a Contact and optionally an Opportunity from one Lead, and copies values across using a mapping. According to Salesforce Help, information in the standard Lead fields appears in the standard fields on the Contact, Account and Opportunity. Custom Lead fields only move if you map them.

    You choose at conversion whether to attach to an existing Account or Contact or create new ones. Salesforce shows possible duplicate matches when conversion starts, and more can appear when you click Convert. Your admin can require people to resolve them first. There is one gap worth knowing: per the same Help article, cross-object duplicate rules aren’t triggered during lead conversion.

    So the screen does warn people. It depends on someone reading the warning.

    How do you stop bad conversions before they happen?

    Three native settings cover most of it. All are admin work, none needs code, and together they take an afternoon.

    1. Make required fields bite at conversion. Salesforce Help lists Require Validation for Converted Leads as the setting to use to avoid duplicate records. Salesforce Ben reports it under Lead Settings, where it enforces validation on the new records. With it on, a validation rule on Account or Contact can stop a conversion with a clear message. As reported by Salesforce Ben, “if it’s a field, it can be validated upon conversion”, for example Email or Lead Source. Write error messages a rep can act on, because the generic “There was an error converting the lead” helps nobody.

    2. Check duplicates first, and teach the habit. Duplicate matching rules on Lead, Contact and Account give reps a warning at the right moment. Make sure the rules cover the fields your reps actually have at conversion (email, domain), since the match is only as good as the data. And since cross-object rules don’t run at conversion, don’t count on them as your only guard. Reps still need to choose the existing Account.

    3. Map custom Lead fields on purpose. Mapping is in Setup under Object Manager, Lead, Fields & Relationships, then Map Lead Fields. You need the Customize Application permission, and per Salesforce Help the feature needs Apex Lead Convert. In Lightning Experience a custom Lead field can map to Account, Contact and Opportunity fields at once. Unmapped custom fields are left behind, which is how a “Source campaign” value goes missing without anyone noticing. After you change a mapping, convert a test Lead in a sandbox and read the three new records.

    Also check who holds the Convert Leads permission. Not everyone who can edit a Lead needs to convert one.

    What would a dry run and an undo change?

    A dry run changes when you find the mistake: before it exists. An undo changes how much the mistake costs: one deliberate step instead of a cleanup afternoon.

    That is my opinion, not a Salesforce position. The native screen warns, but it doesn’t show you the finished result and it can’t take it back. If you convert a few Leads a week, the three settings above are probably enough. If many people convert many Leads, and some of them are bulk-converted from a list, the cost of one wrong conversion multiplies and a preview-and-undo layer starts to earn its keep.

    What to do Monday:

    1. Open Setup, then Lead Settings, and check Require Validation for Converted Leads. Write down whether it is on.

    2. Convert a test Lead in a sandbox and compare the Lead’s custom fields with the new Account, Contact and Opportunity. List what didn’t arrive.

    3. Check which profiles and permission sets hold Convert Leads, and trim any that shouldn’t.

    4. Find the last wrong conversion and note what fixing it cost. That is your case for any further tooling.

    Where we come in

    Slipway, by GTM Cloud, is a configurable Convert screen for Salesforce, in early access. It shows a dry run of what would be created or updated before anything is saved, records every conversion, and lets you undo one after showing exactly which records would be deleted. Undo deletes what the conversion created, so check first if people have worked on those records. Read more on the Slipway page.

    Questions people ask

    Can you convert a lead back to a lead in Salesforce?

    Not with a supported feature. Salesforce Help says a lead conversion can’t be reversed. The usual routes are to repair the new records by hand, delete them and recreate the Lead, or restore from a backup. Each has a cost, and backups only help if you took one before converting.

    Why can’t I find a converted lead in Salesforce?

    According to Salesforce Help, once a Lead is converted it no longer appears in search unless your admin has given you the View and Edit Converted Leads permission. The record still exists. You can find it in reports by filtering on the Converted field.

    Do validation rules run when a lead is converted?

    They do when Require Validation for Converted Leads is on in Lead Settings, per Salesforce Help and as reported by Salesforce Ben. With it on, validation rules and automation on the new Account, Contact and Opportunity are enforced, so a bad conversion can be stopped with a clear message.

    Sources