Use the CRM Import tool to bring records into Wingform from CSV files.
Open the Import tool here:
https://app.wingform.com/crm/import
The Import tool works one record type at a time. One CSV file should import Leads, Contacts, Companies, or Tasks. Do not use one file for mixed record types.
What you can import
Leads file
Creates Lead records in the CRM.
Contacts file
Creates Contact records in the CRM.
Accounts or Companies file
Creates Company records in the CRM.
Opportunities file
Creates Task records in the CRM.
If you are importing files exported from Salesforce, import them in this order:
Accounts → Contacts → Leads → Opportunities
This order matters because Contacts and Opportunities can be linked to Companies by external ID.
Step 1: Upload the CSV file
Drag a CSV file into the upload area, or select it from your device.
Wingform reads the file and tries to detect the record type from the file name.
For example:
A file named Contacts.csv is treated as Contacts.
A file named Accounts.csv is treated as Companies.
A file named Leads.csv is treated as Leads.
An Opportunities file is treated as Tasks.
If the detected record type is wrong, change it before continuing.
Step 2: Map your columns
In the Configure step, match each CSV column to a CRM field.
The mapping screen shows four main columns:
CSV Column
The column header from your file.
Sample
An example value from the first data row.
CRM Field
The Wingform field the column should import into.
Status
Shows whether the column is mapped, skipped, or needs attention.
Required fields
Some record types need specific data before they can be imported.
Lead
Needs a Lead name, or enough first and last name data to build a Lead name.
Contact
Needs at least one mapped value with data.
Company
Needs a Company name.
Task
Needs a Task title.
You cannot preview the import until the required fields are mapped.
Creating custom fields during import
If a CSV column does not match an existing CRM field, you can import it as a custom field.
Choose New custom field, then complete the custom field settings.
Label
The name users see in the CRM.
Field key
The internal key generated from the label.
Field type
Choose Text, Number, Date, Money, Select, or Boolean.
Show in table
Turn this on if you want the field to appear as a table column after import.
If you do not show the custom field in the table immediately, you can still enable it later from the Columns picker.
Step 3: Preview the import
Preview shows the first rows as they will be imported.
Use this step to check:
Whether names look correct.
Whether dates are parsed correctly.
Whether amounts are cleaned correctly.
Whether required fields are present.
Which rows will be imported.
Which rows will be skipped.
A row is skipped when it does not have enough data to create the selected record type.
A skipped row is not always an error. It usually means the row is incomplete.
Step 4: Run the import
When you run the import, Wingform creates the records one by one and shows progress.
After the import finishes, the result card shows:
How many records were created.
How many rows were skipped.
Any row-level errors.
Any relationship warnings.
Image to insert:
Import result card.Importing related files
When importing related files, use Import another file from the result screen instead of reloading the page.
This keeps the current import session active.
The import session is important because Wingform remembers Company external IDs during the session.
Those external IDs are used to link later imported Contacts and Tasks to the right Companies.
Why Companies should be imported first
Contacts and Opportunities can link to Companies by external ID.
For this to work:
Import Accounts or Companies first.
Wingform stores their external IDs during the import session.
Import Contacts and Opportunities next.
Wingform uses the stored external IDs to connect them to the right Companies.
If you import Contacts or Opportunities before Companies, the records can still be created, but the Company relationship may be missing.
Relationship warnings
A relationship warning means Wingform created the row but could not connect it to another record.
The most common reason is that a Contact or Task references a Company external ID that has not been imported in the current session.
To fix this:
Import the Companies file first.
Use Import another file.
Import the related Contacts or Opportunities file again.
Important limitations
Each CSV file should contain one record type.
Mixed files are not supported.
There is no automatic duplicate detection.
Importing the same file twice can create duplicate records.
Leads are not automatically linked to Companies during import.