Before you start
- Authorized access to the import workbench and the correct target installation.
- A copy of the source file/sheet, expected row count and agreed mapping/duplicate policy.
- A small sample for verification. Existing import defaults and saved browser settings must be reviewed for the current business, not trusted as universal defaults.
Open in your admin application
Use your installation’s admin address with one of these routes. Replace {id} with the actual record identifier.
/bulk-upload-workbench/leads/unassigned-leads/lead?LeadID={id}Prepare and preview the import
Load the source
Open
/bulk-upload-workbench. In Step 1: Data Source use Load File, or Load Google Sheet with Sheet ID and Tab. Confirm the selected dataset and source row count in Data Preview.Map columns explicitly
In Step 2: Map Columns inspect source-to-target mappings and transforms. Typical target fields include Company, FirstName, LastName, Phone, Email, address, Source, Priority, StatusID, SalesRepresentativeID, ImportKey and CampaignID. Preserve stable external/import identity where supplied.
Replace inappropriate defaults
Check default owner, status, source, opportunity values and tags for this batch. The current workbench contains deployment-oriented defaults and persists browser settings; a mapping reused from another batch can silently describe the wrong business context.
Choose Test Import
This transforms the dataset and sets import column mappings, then exposes Step 3: Ready to Import. Inspect the transformed preview and sample rows. It is not proof that production records were imported successfully.
Commit only the intended batch
After verifying mapping and row count, choose Import Now. This invokes the lead import. Retain the source/mapping and import result for reconciliation.
Reconcile in the lead views
Inspect representative records and available counts/import identifiers. Confirm contact formatting, owner, source, campaign and intended duplicate handling before repeating or expanding the batch.
Review duplicates and bulk actions
Review potential duplicate rows
On a lead compare identity, contacts, address, notes, source and owner for each possible duplicate. Similar company names are not sufficient evidence.
Treat merge as irreversible
The UI prompts: That which has been merged cannot be unmerged. Are you sure? Decide the survivor and preserve relevant context before confirming an authorized merge. Do not start with Auto Merge just to clear warnings.
Scope bulk changes first
On an eligible lead list use filters, Select Rows and the exposed Bulk Actions. Check selected count, target owner/status and a sample of selected records before the final action. Verify a sample afterward.
Fields & records
| Field / record | Meaning or use |
|---|---|
| ImportKey | Source/import identity for tracing batches or repeated imports. |
| Test Import | Transformation/preview stage; not a live-record verification report. |
| Import Now | The data-changing import operation. |
| Selected row count | Scope of a bulk action, not necessarily the total filtered dataset. |
Verify the result
- Source and transformed row counts/mappings are understood.
- Imported samples have correct owner, source, status and identity.
- Bulk/merge results preserve the intended customer context.
Troubleshooting
| What you see | What to check or do |
|---|---|
| Wrong owner or source after import | Inspect default mappings and saved settings before rerunning. |
| Test Import looked fine but no leads exist | Only Import Now calls the import operation. Inspect its result. |
| Unexpected duplicates | Review ImportKey/source identity and duplicate policy before re-importing the file. |
Version & scope
Procedure checked against current Feeding Frenzy forms and services. Source verification is not a claim that a live payment, message, customer transaction or full operator run occurred.
Public guides describe shared controls, records and configuration boundaries using fictional data. Tenant URLs, credentials, customer records, provider identifiers and installation-only procedures belong in customer-controlled documentation and are excluded from public pages and search.
- Version
- 2.0.0
- Change source
- Current Feeding Frenzy forms/services plus reconciled Wiki topics
- Feedback key
guide:imports
Feedback records only the page, guide ID and yes/no choice. It never records documentation search text.
Implementation references (3)
FeedingFrenzy.Admin/wwwroot/kScripts/BulkUpload/BulkUploadWorkbench.ks.htmlFeedingFrenzy.Admin/wwwroot/kScripts/Leads/Leads.Objects.ks.htmlFeedingFrenzy.Admin/wwwroot/kScripts/Leads/Lead.Details.ks.html