Skip to main content

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
You need to import this data accurately while:
  • 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.
  1. Open your source data
    • What columns do you have?
    • How many records?
    • What’s the data quality like?
  2. Audit for issues:
  3. 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.
  1. Navigate to Import
    • Go to Settings > Import Data
    • Select Customers
    • Click Download Template
  2. Review the template columns:

Step 3: Prepare Your Data (30-60 minutes)

This is the most important step. Don’t skip or rush it.
  1. Copy template structure
    • Create new sheet using template columns
    • Or add template columns to your existing data
  2. Clean your data: Deduplicate:
    Standardize phone numbers:
    Fix addresses:
    Handle missing data:
  3. Final prepared data:
  4. 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.
  1. Create a test file:
    • Copy 5-10 representative records
    • Include edge cases (long names, special characters)
    • Save as separate test CSV
  2. Run the test import:
    • Go to Settings > Import Data
    • Select Customers
    • Upload your test file
  3. Map columns: The system shows your columns and asks you to match them:
  4. Preview the import:
    • Review how records will look
    • Check for any warnings
    • Verify data appears correctly
  5. Complete test import:
    • Click Import
    • Wait for completion
  6. Verify test records:
    • Go to Customers
    • Find your test records
    • Open each one and verify data is correct
  7. 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.
  1. 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
  2. Upload the full file:
    • Go to Settings > Import Data
    • Select Customers
    • Upload your prepared CSV
  3. Verify column mapping:
    • Should match your test
    • Double-check each column
  4. Preview:
    • Review record count (matches expectation?)
    • Check sample records
    • Note any warnings
  5. Import:
    • Click Import
    • Wait for completion
    • Note: Large imports may take several minutes
  6. Review import results:

Step 6: Handle Import Errors (if any)

Review and resolve any failures.
  1. Download error report:
    • Most systems provide an error log
    • Shows which records failed and why
  2. Common errors and fixes:
  3. 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.
  1. Check record count:
    • Go to Customers
    • Total should match import count
    • (Plus any existing records)
  2. Random spot checks: Pick 10 random customers and verify:
  3. Check edge cases:
    • Longest customer name
    • Special characters (& ’ ” etc.)
    • International addresses
    • Records with minimal data
  4. Search test:
    • Search for specific customers
    • Verify they’re findable

Step 8: Post-Import Tasks

Clean up and document.
  1. Archive source file:
    • Save final import CSV
    • Note date and record count
    • Store securely
  2. Document the import:
  3. 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:
  1. Export current data first
  2. Merge your updates with exported data
  3. Use update/merge import option (if available)
  4. 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
Test Import:
  • Small test file created
  • Test import successful
  • Data verified correct
  • Test data cleaned up
Full Import:
  • Team notified
  • Full file uploaded
  • Columns mapped correctly
  • Preview reviewed
  • Import completed
Verification:
  • Record count matches
  • Spot checks passed
  • Edge cases verified
  • Search works
Documentation:
  • Source file archived
  • Import documented
  • Stakeholders notified

Sample Data Transformation

Before (messy):
After (clean, ready for import):
Transformations applied:
  • 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 →