How to Create Multiple Custom Fields in Salesforce Quickly
Create custom fields in Salesforce in bulk - the Setup wizard, metadata deployment, and in-browser field creation - plus the naming rules to settle first.
Updated 2026-09-09
The Setup field wizard is fine for one field and painful for twenty: six screens each, and the field-level security step repeated every time.
When a project needs a batch of fields on one object, there are three faster paths.
Settle the conventions before the first field
- API naming: pick a convention and apply it to every field in the batch - renaming later breaks integrations and formulas.
- Field type and length: text vs picklist decisions are expensive to reverse once data lands.
- Description and help text: required by most governance reviews, and cheap to write now, tedious to backfill.
Option 1 - the Setup wizard
Object Manager → Fields & Relationships → New. Reliable, guided, and the right choice for a single field with an unusual type such as a formula or roll-up summary.
Option 2 - metadata deployment
- Author the field XML, deploy with the Salesforce CLI, and keep the definitions in version control.
- Best for repeatable, reviewable changes that must move sandbox to production.
- Highest setup cost, lowest cost per repeat.
Option 3 - create fields in the browser
TurboKit's field creator adds fields from within Salesforce without the full Setup navigation, which suits the middle case: a handful of fields on one object, needed now, not worth a deployment pipeline.
After the fields exist
- Grant field-level security to the profiles or permission sets that need it - new fields are hidden from everyone but System Administrator by default.
- Add them to the page layouts and, where relevant, the compact layout.
- Update the report types if the fields should be reportable.
Frequently asked questions
- Can I create Salesforce fields from a spreadsheet?
- Not natively. You can generate metadata XML from a spreadsheet and deploy it with the CLI, which is the usual approach for large batches.
- Why can't anyone see the field I just created?
- New custom fields are visible only to System Administrator until you grant field-level security and add the field to a page layout.
- Can I change a field's type after creation?
- Sometimes. Salesforce allows certain conversions (text to picklist, for example) with data-loss warnings; others require creating a new field and migrating the data.
More from the Admin How-To
- How to Log In as Another User in SalesforceLog in as another Salesforce user to reproduce a permission issue - the Setup route, the permissions required, and how to switch orgs without losing your place.
- How to Retrieve Salesforce Metadata Without the CLIRetrieve Salesforce metadata - objects, fields, layouts, profiles - using the Metadata API, the CLI, or an in-browser viewer, and when each is worth the setup.
- How to Write Salesforce Queries Without Knowing SOQL (AI SOQL)Describe the records you want in plain English and get a runnable SOQL query back - how AI SOQL builders work, what to check before you run the result, and where they still fall short.
- Change Sets vs Metadata API Deployments: Which to UseChange sets and Metadata API / CLI deployments solve the same problem differently. Here is when each one is the right choice, and what a change set genuinely cannot do.
- How to Check Field-Level Security in Salesforce FastCheck field-level security in Salesforce without clicking through Setup: where FLS lives, how it interacts with profiles and permission sets, and faster ways to read it.
- How to Check Salesforce Org LimitsCheck Salesforce org limits - API calls, data storage, file storage, and daily email - from Setup, the limits API, and the browser, before you hit them.