Importing Customer Data
How to bulk import customers from a spreadsheet into Taskr without data disasters.📋 The Scenario
Your company is migrating from an old system (or spreadsheets) to Taskr. You have:- 250 customer records in Excel
- Associated contact information
- Multiple locations per customer in some cases
- Avoiding duplicates
- Maintaining data quality
- Setting up proper relationships
- Being able to roll back if something goes wrong
🎯 What You’ll Learn
- Preparing data for import
- Using import templates
- Handling complex data relationships
- Validating imported data
- Recovering from import errors
📝 Prerequisites
- Admin or Owner role
- Source data in spreadsheet format
- Time to prepare and verify data (don’t rush this!)
- Backup of original data
👣 Step-by-Step Walkthrough
Step 1: Assess Your Data (15 minutes)
Understand what you’re working with before touching Taskr.-
Open your source data
- What columns do you have?
- How many records?
- What’s the data quality like?
-
Audit for issues:
-
Example source data:
Issues spotted:
- ABC Company appears twice (two contacts, same company)
- XYZ has no contact name
- Phone formats inconsistent
- Test Customer has invalid email, missing address
- Need to decide: one record per company, or per contact?
Step 2: Download the Import Template (2 minutes)
Get Taskr’s official template for best results.-
Navigate to Import
- Go to Settings > Import Data
- Select Customers
- Click Download Template
-
Review the template columns:
Step 3: Prepare Your Data (30-60 minutes)
This is the most important step. Don’t skip or rush it.-
Copy template structure
- Create new sheet using template columns
- Or add template columns to your existing data
-
Clean your data:
Deduplicate:
Standardize phone numbers:Fix addresses:Handle missing data:
-
Final prepared data:
-
Save as CSV:
- File > Save As
- Choose CSV format
- Use UTF-8 encoding if prompted
Step 4: Do a Test Import (10 minutes)
Never import your full dataset first. Test with a small sample.-
Create a test file:
- Copy 5-10 representative records
- Include edge cases (long names, special characters)
- Save as separate test CSV
-
Run the test import:
- Go to Settings > Import Data
- Select Customers
- Upload your test file
-
Map columns:
The system shows your columns and asks you to match them:
-
Preview the import:
- Review how records will look
- Check for any warnings
- Verify data appears correctly
-
Complete test import:
- Click Import
- Wait for completion
-
Verify test records:
- Go to Customers
- Find your test records
- Open each one and verify data is correct
-
Clean up test data:
- Delete the test customer records
- (Or mark as inactive with clear “TEST” naming)
Step 5: Perform Full Import (15 minutes)
Now you’re ready for the real thing.-
Final preparations:
- Test import successful
- Full data file ready
- Backup of source data saved elsewhere
- Team notified (don’t import while others are adding customers)
- Time set aside to verify after
-
Upload the full file:
- Go to Settings > Import Data
- Select Customers
- Upload your prepared CSV
-
Verify column mapping:
- Should match your test
- Double-check each column
-
Preview:
- Review record count (matches expectation?)
- Check sample records
- Note any warnings
-
Import:
- Click Import
- Wait for completion
- Note: Large imports may take several minutes
-
Review import results:
Step 6: Handle Import Errors (if any)
Review and resolve any failures.-
Download error report:
- Most systems provide an error log
- Shows which records failed and why
-
Common errors and fixes:
-
Fix and reimport failures:
- Create new CSV with just failed records
- Correct the issues
- Import the corrected records
Step 7: Verify Imported Data (15 minutes)
Spot-check to ensure quality.-
Check record count:
- Go to Customers
- Total should match import count
- (Plus any existing records)
-
Random spot checks:
Pick 10 random customers and verify:
-
Check edge cases:
- Longest customer name
- Special characters (& ’ ” etc.)
- International addresses
- Records with minimal data
-
Search test:
- Search for specific customers
- Verify they’re findable
Step 8: Post-Import Tasks
Clean up and document.-
Archive source file:
- Save final import CSV
- Note date and record count
- Store securely
-
Document the import:
-
Notify stakeholders:
- Let the team know import is complete
- Note any special considerations
⚡ Pro Tips
Data Preparation
Import Safety
When Things Go Wrong
🔄 Variations
Importing Locations
Same process, different template. Additional considerations:- Link to existing customers (need customer ID or name)
- Include access information
- Add building details
Importing Assets
More complex because of relationships:- Needs location or customer reference
- May need asset types created first
- Include compliance dates if available
Updating Existing Records
If customers already exist:- Export current data first
- Merge your updates with exported data
- Use update/merge import option (if available)
- Or manually update changed records
❓ Common Questions
Q: What if I have 1000+ records?Same process, but: 1) Allow more time, 2) Consider importing in batches of 250-500, 3) Verify more thoroughly.Q: What about customer contacts?
Contacts are usually a separate import. Import customers first, then import contacts with customer references.Q: Can I undo an import?
Not automatically. You’d need to manually delete imported records or restore from backup. This is why testing is critical.Q: My data has columns that don’t match the template?
You can: 1) Skip those columns, 2) Map to custom fields if available, 3) Include in notes field.Q: What about locations for each customer?
Import customers first, then locations. Location import will reference customers by name or ID.
✅ Import Checklist
Preparation:- Source data assessed
- Template downloaded
- Data cleaned and formatted
- Duplicates resolved
- File saved as CSV
- Small test file created
- Test import successful
- Data verified correct
- Test data cleaned up
- Team notified
- Full file uploaded
- Columns mapped correctly
- Preview reviewed
- Import completed
- Record count matches
- Spot checks passed
- Edge cases verified
- Search works
- Source file archived
- Import documented
- Stakeholders notified
Sample Data Transformation
Before (messy):- Standardized company name format
- Consolidated duplicate into single record
- Fixed phone format
- Split address into components
- Invalid email removed, added to notes
- Additional contact preserved in notes
← Previous: Setting Up New User | Back to Examples | Next: Troubleshooting User Issues →