General process
Migrating from any CRM follows these steps:Exporting from common CRMs
Redtail
Key Redtail fields to export:
- Contact information (name, email, phone)
- Categories and tags
- Family/household relationships
- Notes and activities
- Custom fields
Salesforce
Salesforce considerations:
- Export Contacts and Accounts separately
- Include relationship fields
- Export related objects (tasks, notes) separately
Junxure
Other CRMs
Most CRMs offer CSV export:- Look for “Export,” “Data Export,” or “Backup” options
- Select the records to export
- Choose CSV format
- Include all relevant fields
If your CRM doesn’t have CSV export, contact their support for data extraction options.
Preparing your data
Clean your data first
Before importing, clean your data: Remove duplicates:- Identify duplicate contacts
- Decide which record to keep
- Remove or merge duplicates
- Phone numbers: (555) 123-4567
- States: Two-letter abbreviations (CA, not California)
- Dates: YYYY-MM-DD format
- Required fields need values
- Use placeholders if necessary
Required fields
Slant requires these fields for import:| Record type | Required fields |
|---|---|
| Clients/Prospects | Household name, at least one person |
| People | First name, last name |
| Contacts | Name |
Recommended fields
Include these for complete records:| Field | Why important |
|---|---|
| Email addresses | Communication tracking |
| Phone numbers | Contact information |
| Addresses | Complete client profile |
| Tier/Category | Service level classification |
| Assigned advisor | Proper assignment |
Field mapping
Common mappings
Map your CRM fields to Slant fields:| Your CRM field | Slant field |
|---|---|
| First Name | person.first_name |
| Last Name | person.last_name |
| person.email | |
| Home Phone | person.phone |
| Street Address | person.address_line_1 |
| City | person.city |
| State | person.state |
| Zip | person.postal_code |
| Account Name | household.name |
| Type/Category | household.tier |
Handling unmapped fields
For fields that don’t have direct mappings:- Custom fields: Import to Slant custom fields
- Notes: Import as note records
- Tags: Map to Slant tags
- Other: Consider if data is still needed
Import process
Step 1: Upload CSV
Step 2: Map columns
Step 3: Preview and validate
Step 4: Import
Multiple imports
Import order
For complete migrations, import in this order:- Households/Clients — Create the client records first
- People — Add people to households
- Contacts — Import professional contacts
- Tasks — Import open tasks
- Notes — Import historical notes
Linking records
After importing related records:- People link to households by matching household name
- Tasks link by client name or ID
- Notes link by client name or ID
Post-import cleanup
Verify data
After importing:Fix issues
Common post-import fixes:- Merge duplicate records
- Correct field values
- Add missing information
- Adjust assignments
Clean up old CRM
Once verified:- Keep old CRM accessible during transition
- Set a date to fully decommission
- Export final backup before closing
Getting help
Assisted migration
For complex migrations, Slant offers assisted migration:- Data analysis and mapping assistance
- Import execution and verification
- Post-import support
Support resources
Tips for success
Start with a test batch
Before importing everything:- Export a small sample (10-20 records)
- Import the sample
- Verify results
- Adjust mapping if needed
- Then import the full dataset
Keep your old data
Don’t delete your old CRM data until:- Full import is verified
- Team is comfortable with Slant
- Compliance retention requirements met
Document your mapping
Keep a record of:- How you mapped fields
- Any data transformations made
- What was not imported and why