How mapping works
When you upload a CSV, Slant:- Reads your column headers
- Attempts auto-mapping based on common names
- Shows you the proposed mapping
- Lets you adjust as needed
Mapping interface
For each column in your file:| Element | Description |
|---|---|
| Source column | Your CSV column name |
| Sample data | First few values from your file |
| Target field | Slant field to map to |
| Status | Mapped, unmapped, or skipped |
Standard field mappings
Person fields
| Common CSV names | Map to Slant field |
|---|---|
| First Name, FirstName, Given Name | person.first_name |
| Last Name, LastName, Surname, Family Name | person.last_name |
| Email, Email Address, E-mail | person.email |
| Phone, Phone Number, Mobile, Cell | person.phone |
| Home Phone, Home | person.home_phone |
| Work Phone, Office, Business Phone | person.work_phone |
| Address, Street, Street Address | person.address_line_1 |
| Address 2, Unit, Apt | person.address_line_2 |
| City | person.city |
| State, Province | person.state |
| Zip, Postal Code, ZIP Code | person.postal_code |
| Country | person.country |
| Birthday, Date of Birth, DOB | person.date_of_birth |
Household fields
| Common CSV names | Map to Slant field |
|---|---|
| Household, Household Name, Account | household.name |
| Tier, Service Tier, Category | household.tier |
| AUM, Assets | household.aum |
| Source, Lead Source | household.source |
Contact fields
| Common CSV names | Map to Slant field |
|---|---|
| Company, Company Name, Organization | contact.company_name |
| Contact Type, Type, Category | contact.type |
| Website, URL | contact.website |
Task fields
| Common CSV names | Map to Slant field |
|---|---|
| Title, Task, Task Name, Subject | task.title |
| Description, Notes, Details | task.description |
| Due Date, Due, Deadline | task.due_date |
| Priority | task.priority |
| Assignee, Assigned To, Owner | task.assignee |
| Client, Household | task.household |
Handling special cases
Date formats
Slant accepts multiple date formats:| Format | Example |
|---|---|
| YYYY-MM-DD | 2024-03-15 |
| MM/DD/YYYY | 03/15/2024 |
| DD/MM/YYYY | 15/03/2024 |
| Month DD, YYYY | March 15, 2024 |
For best results, use YYYY-MM-DD format. This avoids ambiguity between MM/DD and DD/MM.
Phone number formats
Slant normalizes phone numbers. These all work:- (555) 123-4567
- 555-123-4567
- 5551234567
- +1 555 123 4567
Tier values
Map tier values to Slant’s system:| Your value | Maps to |
|---|---|
| A, Tier A, 1, Platinum | A tier |
| B, Tier B, 2, Gold | B tier |
| C, Tier C, 3, Silver | C tier |
| D, Tier D, 4, Bronze | D tier |
Boolean values
For yes/no fields:| Your value | Maps to |
|---|---|
| Yes, Y, True, 1 | True |
| No, N, False, 0 | False |
| (empty) | Not set |
Multiple values
Multiple emails
If a person has multiple emails: Option 1: Separate columnsMultiple phones
Similar to emails:Multiple addresses
For multiple addresses, import the primary address. Add additional addresses manually after import.Custom field mapping
Map to existing custom fields
If you’ve created custom fields in Slant:1
Find your column
Locate the column in the mapping interface.
2
Open field selector
Click the target field dropdown.
3
Find custom fields
Scroll to “Custom Fields” section.
4
Select field
Choose your custom field.
Create custom fields during import
If you need a new custom field:- Complete the current import without that column
- Create the custom field in settings
- Import again with just that column, updating existing records
Skip columns
Not every column needs to be imported:1
Find the column
Locate the column to skip.
2
Select Skip
In the target field dropdown, choose “Skip this column.”
3
Column ignored
Data from this column won’t be imported.
When to skip
Skip columns that:- Contain internal IDs from other systems
- Have data you don’t need in Slant
- Duplicate information in other columns
- Contain notes you’ll add differently
Auto-mapping
How auto-mapping works
Slant recognizes common column names:- “First Name” → person.first_name
- “Email” → person.email
- “Phone” → person.phone
Verify auto-mapping
Always check auto-mapped fields:- Review each mapping
- Check sample data looks correct
- Adjust any incorrect mappings
Troubleshooting mapping
Column not recognized
If Slant doesn’t auto-detect a column:- Manually select the target field
- Or rename the column header in your CSV to match common names
Data appears wrong in preview
If mapped data looks incorrect:- Check you selected the right field
- Verify data format matches expectations
- Look for encoding issues (special characters)
Can’t find the right field
If the Slant field you need doesn’t appear:- Check you’re importing the right record type
- The field may need to be created as a custom field
- Some fields are read-only and can’t be imported
Mapping resets
If your mapping disappears:- Don’t navigate away during mapping
- Complete the import in one session
- If page reloads, you may need to re-upload
Save mapping templates
For recurring imports with the same structure:1
Complete mapping
Set up all column mappings.
2
Save template
Click Save mapping as template.
3
Name template
Give it a descriptive name.
Use a saved template
1
Upload file
Upload your CSV as usual.
2
Apply template
Click Use saved mapping.
3
Select template
Choose your saved mapping.
4
Verify
Confirm mapping is still correct.
Best practices
Name columns clearly
Use unambiguous names:- ✓ “First Name” not “Name 1”
- ✓ “Home Phone” not “Phone”
- ✓ “Work Email” not “Email 2”
Check sample data
For each mapping, verify:- Sample data looks correct in preview
- No obviously mismatched data
- Formatting is recognized
Document your mappings
Keep a record of how you mapped fields, especially for:- Non-obvious mappings
- Custom field usage
- Skipped columns and why