Wizard
A wizard in Salesforce is a guided, multi-step user interface that walks a person through a structured task one screen at a time, validating input before letting them move forward.
Definition
A wizard in Salesforce is a guided, multi-step user interface that walks a person through a structured task one screen at a time, validating input before letting them move forward. Instead of presenting every option at once, a wizard breaks a job into a short sequence of focused steps, so the user always knows what to do next.
Salesforce ships several built-in wizards, including the Data Import Wizard for loading records and various setup wizards inside the Setup menu. When admins need a custom guided flow, they usually build one as a Screen Flow in Flow Builder, which provides Next and Previous navigation, stages, and a progress indicator without writing code.
How wizards work and where you meet them in Salesforce
A pattern, not a single product
A wizard is a user-experience pattern rather than one named feature. The idea is simple. When a task has many inputs or branching decisions, you split it into ordered steps and reveal one step at a time. Each step collects a small amount of information, checks it, and only then advances. This reduces errors and lowers the mental load on the person doing the work. Salesforce uses this pattern in many places. The Data Import Wizard guides you through choosing an object, picking a file, mapping fields, and starting the load. Setup contains task-specific wizards that turn on features or create records with sensible defaults. Schema Builder and the Lightning App Builder include guided creation steps for new objects and apps. Because the pattern is so common, the word wizard is best understood as a description of behavior. It tells you to expect a short, linear sequence with guardrails, not a particular technology underneath. The same outcome could be delivered by a packaged tool, a Screen Flow, or a custom component.
The Data Import Wizard, step by step
The Data Import Wizard is the wizard most admins meet first. You launch it from Setup by entering Data Import Wizard in Quick Find, then clicking Launch Wizard on the welcome page. The first step asks what kind of data you are importing. It supports accounts and contacts, leads, campaign members, person accounts, solutions, and custom objects. The next step asks whether you want to add new records, update existing ones, or do both at once. You then choose your CSV file and tell the wizard how to match incoming rows to existing records. The mapping step lines up each column in your file against a Salesforce field, auto-matching what it can and leaving the rest for you to map by hand. A review step lets you confirm settings before you commit. When you click Start Import, the job runs in the background and emails you when it finishes. The wizard handles up to 50,000 records per run. For larger volumes or unsupported objects, Salesforce points you to Data Loader instead.
Screen Flows as the modern wizard builder
When the built-in wizards do not fit, Screen Flows are the declarative way to build your own. A Screen Flow is an interactive, user-facing flow made of screens, where each screen acts like one step in the sequence. You drag screen components onto each step to collect or display data, including text inputs, picklist choices, lookups, and a repeater for capturing several records at once. Flow Builder gives every Screen Flow the navigation a wizard needs. Users move forward with a Next button and back with a Previous button, and the last screen shows a Finish button. You can wire decisions between screens so the path branches based on earlier answers. Validation on each input means a user sees a problem right away rather than at the end. Because the flow is built point and click, an admin can design a multi-step guided experience without code and change it later without a deployment. This is why most new custom wizards in Salesforce start life as Screen Flows.
Stages and progress indicators
A good wizard tells people how far along they are. In Screen Flows, that sense of place comes from stages and a progress indicator. A stage represents a major phase of your process, such as Gather Details, Review, and Confirm. You define the stages your flow uses, then assign screens to them so the flow knows which stage is active at any moment. The progress indicator renders those stages visually at the top of the flow, highlighting the current step and showing what still remains. Salesforce has also added built-in visual progress indicators for Screen Flows, so you get this guidance with less manual setup. Stages are dynamic, which means you can add or skip them at runtime based on the user's choices. If a user picks a path that does not need the billing step, you can leave that stage out of the indicator. The result feels like a familiar checkout or setup wizard, where the steps across the top reassure the person that the end is in sight.
Where you can place a custom wizard
Building the wizard is only half the job. You also decide where users meet it. A Screen Flow can be embedded directly on a Lightning record page or app page through the Lightning App Builder, so it sits alongside the record it relates to. You can launch it from a button, a quick action, a navigation tab, or the utility bar, which keeps the wizard one click away during everyday work. For people outside your org, you can surface the same flow on an Experience Cloud site, including public pages that guest users can reach without logging in. This makes Screen Flows a good fit for self-service tasks like event registration, support intake, or guided onboarding. Developers can also invoke a flow from Apex or call it through the REST API when a wizard needs to run as part of a larger process. Choosing the right placement matters as much as the steps themselves, because a wizard only helps if users find it at the moment they need to complete the task.
Designing wizards that people finish
The point of a wizard is completion, so design choices should protect the path to Finish. Keep each step focused on a single decision or a small group of related fields. Long screens crowded with inputs defeat the purpose and push people to abandon the flow. Use clear labels and help text so the user never has to guess what a field wants. Validate as early as you can. Catching a bad email on the screen where it was typed is kinder than failing at the end. Let people go back with Previous so a mistake does not force a restart. Show progress through stages so the effort feels bounded. For data wizards, prepare the source first. A clean CSV with consistent column names maps faster and produces fewer surprises. Test the full sequence as a real user before you release it, including the branches, because a step that works in isolation can still strand someone when the order is wrong. A wizard that respects the user's time earns the completed records or configurations you were after.
Build a custom wizard with a Screen Flow
Build a custom wizard as a Screen Flow in Flow Builder. This gives you Next and Previous navigation, stages, and a progress indicator without code.
- Create a Screen Flow
From Setup, open Flow Builder and create a new flow. Choose Screen Flow as the type so the flow runs as an interactive, user-facing sequence of screens.
- Add a screen for each step
Drag a Screen element onto the canvas for every step in your task. Add screen components such as text inputs, picklist choices, and lookups to collect what that step needs.
- Define stages and a progress indicator
Create stages for the major phases of your process and assign screens to them. Add a progress indicator so users can see the current step and what still remains.
- Branch and validate
Use Decision elements to route users based on earlier answers, and set validation on inputs so problems surface on the screen where they occur, not at the end.
- Place the wizard where users work
Activate the flow, then embed it on a Lightning page, a quick action, or an Experience Cloud site so users can reach it at the moment they need it.
A field or display element on a step, such as a text input, picklist, lookup, or repeater, that collects or shows data.
A major phase of the flow used to power the progress indicator and tell users where they are in the sequence.
Built-in Next, Previous, and Finish controls that move users between steps and complete the wizard.
Where the flow runs, including a Lightning record page, a quick action, the utility bar, or an Experience Cloud site.
- Crowding one screen with too many inputs defeats the purpose. Keep each step focused on a single decision or a small set of related fields.
- Guest users on a public Experience Cloud site need the flow shared for guest access, or external users will not be able to run it.
- Test every branch as a real user before release. A step that works alone can still strand someone when the path order is wrong.
Trust & references
Cross-checked against the following references.
- Getting Started with Screen FlowsSalesforce
- Import Data with the Data Import WizardSalesforce
Straight from the source - Salesforce's reference material on Wizard.
- Use Screen Flows to Interact with UsersSalesforce
- Import LimitsSalesforce
Hands-on resources to go deeper on Wizard.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Wizard?
Q2. What are examples?
Q3. Can you build custom wizards?
Discussion
Loading discussion…