How to Import Spreadsheet Into Paxelo: Step-by-Step (2026)

TL;DR

Importing a spreadsheet into a sales route planner means uploading a CSV, XLS, or XLSX file containing your customer and prospect list so the software can geocode addresses, apply account priorities and visit frequencies, and build optimized routes and territory maps. The process involves preparing clean data, uploading the file, mapping columns to system fields, validating for errors, and confirming the import. This guide walks through each step with a focus on outside sales workflows in Paxelo, covering the fields that matter for B2B territory coverage, the errors that trip up sales ops teams, and how to get a rep’s entire book of business into the system without breaking anything.

Every outside sales team has a spreadsheet. Maybe it’s the master account list in Excel. Maybe it’s a CSV export from Salesforce or HubSpot. Maybe it’s a Google Sheet that the regional manager has maintained for three years with color-coded tabs and conditional formatting that no one else understands.

That spreadsheet is the starting point. Getting it into a route planner like Paxelo, cleanly and completely, is what separates a team that’s optimizing routes by lunch from one that’s still fixing import errors on Wednesday.

This guide covers the full process: file formats, which fields outside sales teams actually need, step-by-step instructions (with Paxelo-specific details), common errors, and the best practices that prevent wasted hours.

What Does “Import Spreadsheet” Mean for Outside Sales?

For outside sales teams, importing a spreadsheet means uploading your account list, customer book, or prospect file into routing and territory software so it can plot accounts on a map, assign them to territories, apply visit frequency rules, and generate optimized daily routes.

Three related terms come up constantly, and they mean different things:

• Import is a one-time (or periodic) push of data from a file into the system. The software reads rows, maps columns, and creates account records.
• Upload technically just means transferring the file to the server. The import is the processing that happens after.
• Sync implies an ongoing, often bidirectional connection between two systems, like a CRM feeding accounts automatically. Paxelo has Salesforce and HubSpot integrations on the roadmap, but today, CSV/bulk import is how most teams get started.

For sales leaders, the import is how you go from “I have a list of 400 accounts across three territories” to “I can see coverage gaps, visit cadence compliance, and which A-tier accounts haven’t been touched in six weeks.” For reps, it’s how the customer book on their laptop becomes a prioritized daily run sheet on their phone.

Common File Formats for Spreadsheet Import

Not all spreadsheet files behave the same way during import. Here’s what you’ll encounter:

For maximum compatibility, CSV is the safest choice. Paxelo’s bulk import accepts CSV and Excel files. If you’re exporting from a CRM, most will give you a CSV option, and that’s the one to pick.

One important technical detail: files should use UTF-8 encoding. This ensures special characters (accented customer names, international addresses) transfer correctly.

Practitioners on Reddit and forums consistently report the same frustration with route planner imports: they approach a CSV upload with one simple hope, “just get my spreadsheet into the app.” But headers might be missing, phone numbers lose their leading zeros, and the fear of overwriting good account data or creating hundreds of broken records is real.

What Fields Should Your Spreadsheet Include?

The columns you need for an outside sales import are different from what a delivery dispatcher would use. You don’t need vehicle capacity, package counts, or dock appointment windows. You need the data that drives territory assignment, visit prioritization, and revenue-optimized routing.

Required Fields

• Company Name (the account name your reps know)
• Address, City, State, ZIP (some tools accept a single combined address field; separate columns are more reliable)
• Contact Name (primary contact at the account)
• Phone Number
• Email Address

Fields That Make Routing and Territory Management Work

These aren’t technically required by most import tools, but without them, you’re just putting dots on a map instead of building a system that prioritizes the right accounts.

• Account Priority Tier (A, B, C, or whatever classification your team uses). This drives visit frequency and routing priority in Paxelo. A-tier accounts get scheduled more often and weighted higher in route optimization.
• Visit Frequency Target (weekly, biweekly, monthly, quarterly). Tells the system how often each account should appear on a rep’s schedule.
• Annual Revenue or Order History (dollar value). Paxelo uses revenue data to optimize routes around value, not just geography. A $500K account three miles away should take priority over a $5K account next door.
• Territory Assignment (territory name, region code, or rep name). Links each account to a specific rep or territory for coverage analysis.
• Last Visit Date (MM/DD/YYYY or similar). Helps identify accounts that are overdue for a visit. Paxelo’s coverage analytics flag gaps based on this.
• Account Status (active, prospect, inactive). Lets you filter and segment after import.
• Custom Tags or Industry (e.g., “building materials,” “food service,” “healthcare”). Useful for filtering territory maps and building targeted route days.
• Notes or Special Instructions (gate codes, preferred visit times, decision-maker preferences). Reps rely on these during execution.

A Paxelo-Ready Spreadsheet Template

Here’s a practical column layout that maps cleanly to Paxelo’s bulk import:

If you’re exporting from a CRM, you likely have most of these fields already. The main additions for Paxelo are Priority Tier and Visit Frequency, which you may need to add manually or derive from existing account scoring.

How to Import a Spreadsheet Into Paxelo: Step by Step

The process follows a consistent pattern across route planning tools, but here are the specifics for getting your account list into Paxelo.

1. Prepare Your File

Headers go in row 1. Each row below represents one account. Remove blank rows, merged cells, formulas, and macros. Strip out extra sheets or tabs, as most import tools only process one sheet at a time.

A few things that trip up sales ops teams specifically:

• If your CRM export includes accounts with no physical address (e.g., online-only customers), remove those rows. They can’t be geocoded and will just create validation errors.
• Make sure territory assignments are consistent. “South Texas,” “S. TX,” and “South TX” are three different territories as far as the system is concerned.
• Revenue should be numeric only. No dollar signs, no commas, no “approx.” Just the number.

2. Upload the File

In Paxelo, navigate to the customer management section and select the bulk import option. Select your file from your computer or drag it into the import interface.

Paxelo offers a free plan with up to 50 customers, which means you can test the import process with a small batch at zero risk before committing your full account list.

3. Map Columns to Fields

This is field mapping, and it’s the step most likely to cause problems if rushed. The tool needs to know that your “Company Name” column should populate its Account Name field, that “Priority (A/B/C)” maps to Account Priority Tier, that “Visit Frequency” maps to its scheduling cadence field, and so on.

Field mapping is essentially translation: your spreadsheet speaks one language (your column headers), and Paxelo speaks another (its database fields). Common column headers like “Address,” “Company,” or “Phone” are often auto-mapped without manual intervention.

When auto-mapping fails, you manually match columns by selecting the correct field from a dropdown. The better tools save your mapping configuration so repeat imports go faster, which matters if you’re refreshing account data monthly from CRM exports.

4. Set Rep Start Locations and Territory Parameters

Before or after importing accounts, configure each rep’s settings:

• Start and end locations, whether that’s a home address, branch office, or flexible location. Most outside sales reps start from home and end at home, not a warehouse.
• Maximum driving time or distance per day. This constrains how many stops Paxelo puts on a daily route.
• Territory boundaries. Assign imported accounts to territories so Paxelo’s territory coverage analytics can identify gaps, calculate visit adherence, and generate coverage heatmaps.

5. Validate the Data

Paxelo scans for problems: duplicate accounts, incomplete addresses, unrecognized locations, missing required fields. Good import tools flag these with a clear summary so you can fix them before anything is committed.

Pay special attention to geocoding failures. If an address can’t be resolved to coordinates, that account won’t appear on territory maps or in optimized routes. A typo in one address field can make a $400K account invisible to the system.

6. Confirm and Import

Review the validation results, resolve any flagged issues, and confirm. Account records are created in the system. At this point, Paxelo can generate territory maps, identify coverage gaps, build priority-weighted route schedules, and push daily run sheets to reps.

What Happens After Import: From Spreadsheet to Sales Execution

Getting the data in is step one. What makes importing into a sales-focused platform different from a generic mapping tool is what happens next.

Territory visibility. Once accounts are imported with territory assignments and priority tiers, sales leaders can see coverage heatmaps, spot territories where A-accounts are being neglected, and identify geographic gaps where accounts exist but visits don’t.

Automatic schedule generation. Paxelo uses the visit frequency and priority data from your import to build monthly schedules automatically. Instead of reps manually planning their weeks in a spreadsheet (or not planning at all), the system generates a cadence that ensures the right accounts get visited at the right intervals.

Revenue-optimized routing. With revenue data imported, Paxelo optimizes routes not just for shortest drive time but for maximum revenue coverage. A rep’s Tuesday route prioritizes the $300K account over the $10K account, even if the smaller one is slightly closer.

Prospect discovery. With the Prospect Intelligence add-on, reps see nearby unvisited prospects along their daily route. Accounts you haven’t imported yet surface as opportunities, turning drive time between meetings into pipeline.

None of this works without a clean import. The data you put in determines the quality of every route, territory map, and coverage report that comes out.

Common Spreadsheet Import Errors and How to Fix Them

Knowing what can go wrong saves hours of troubleshooting. These are the errors sales ops teams hit most often.

Missing or inconsistent headers. If row 1 doesn’t contain clear column names, the import tool can’t map fields. If headers are in row 3 or scattered across merged cells, the file may fail entirely.

Inconsistent territory names. “Northeast,” “NE,” “North East,” and “northeast” are four different territories. Standardize before import, or you’ll end up with fragmented territory maps that don’t reflect reality.

Special characters. Curly quotes, non-standard dashes, and unusual symbols in company names or address fields frequently cause parsing failures. EZRoutePlanner’s data quality guide specifically calls out curly quotes and special characters as common culprits.

Macros, formulas, and filters. Route planning tools, including Paxelo, need raw data. Route4Me’s documentation confirms that files containing macros, formulas, or active filters are not supported by most import tools. Replace formulas with their calculated values (Paste Special > Values in Excel) before exporting.

The CSV-in-Excel trap. A widespread issue: if you open a CSV file in Excel, all the comma-separated data sometimes displays in a single column instead of spreading across multiple columns. If imported in this state, the tool sees one giant field per row and the import fails.

Leading zeros stripped from ZIP codes and phone numbers. Excel automatically removes leading zeros from numeric-looking fields. ZIP code 07102 becomes 7102. New Jersey, Connecticut, and Massachusetts reps know this pain well. The fix: format those columns as Text before entering data, or work in CSV with a text editor.

Revenue data with formatting. “$420,000” won’t import as a number. Neither will “420K” or “~400000.” Strip currency symbols, commas, and abbreviations. Just the number: 420000.

Duplicate records. Importing the same spreadsheet twice, or importing a file that contains internal duplicates, creates a mess. If you have the same account listed under two slightly different names (“ABC Supply Co.” and “ABC Supply Company”), you’ll get duplicate records with split visit history. Check for duplicates before importing, and use a unique identifier like an account ID or CRM record number.

Priority tiers with inconsistent values. If some rows say “A” and others say “High” and others say “1,” the system can’t apply consistent priority logic. Pick one convention and apply it across the entire file.

Multi-tab workbooks. If your Excel file has multiple sheets, most tools will prompt you to select one. Forgetting to choose the right tab is a surprisingly common error. If you have territories split across tabs, consolidate them into a single sheet with a Territory column before import.

Best Practices for Importing Your Account List

A clean import saves exponentially more time than fixing bad data after the fact.

1. Back up your original file. Never import from your only copy.
2. Start with a small test batch. Import 10 to 20 accounts first. Review the results, verify field mapping accuracy, check that priority tiers and visit frequencies applied correctly, and fix issues before running the full import. Paxelo’s free plan (up to 50 customers) is built for exactly this.
3. Use CSV for maximum compatibility. It avoids encoding issues, formula artifacts, and multi-tab confusion.
4. Remove blank rows and merged cells. These create phantom records or break column alignment.
5. Standardize address formats. Pick one convention (“Street” vs “St.” vs “St”) and apply it consistently. Include city, state, and ZIP on every row.
6. Standardize territory names and priority tiers. Consistency here is what makes territory maps and coverage reports accurate.
7. Format ZIP codes and phone numbers as Text. This preserves leading zeros.
8. Include revenue data as plain numbers. No dollar signs, no commas, no abbreviations.
9. Add a unique account identifier. An account ID, CRM record number, or similar unique key prevents duplicate records and makes future re-imports cleaner.
10. Verify field mapping before confirming. One wrong mapping can put revenue data into the notes field across hundreds of accounts.
11. Check imported records immediately. Spot-check 5 to 10 accounts on the map to confirm addresses geocoded correctly, territories assigned properly, and priority tiers applied.

Geocoding: What Happens to Your Addresses After Import

When you import a spreadsheet into Paxelo (or any route planner), addresses go through geocoding, the process of converting street addresses into latitude and longitude coordinates. This is what allows the tool to plot accounts on a territory map, calculate drive times between stops, and optimize routes.

Geocoding accuracy depends entirely on input data quality. Typos, missing suite numbers, abbreviated city names, and inconsistent formatting all reduce accuracy. A misplaced account throws off territory coverage analysis and can mean a rep drives past a key customer without knowing it.

For sales teams importing hundreds of accounts, failed geocodes mean accounts that won’t appear on territory maps or in optimized routes. Data preparation directly affects the quality of every route and coverage report the system generates.

Templates vs. Flexible Mapping

There’s a real divide in how tools handle spreadsheet imports. Some require a rigid template with fixed column names and mandatory fields. You download their template, paste your data into it, and upload. Others accept any spreadsheet structure and let you map freely during import.

Template-based imports reduce errors because the structure is predetermined. But they add friction, since you have to reformat your data every time.

Flexible imports work with your spreadsheet as-is. You upload, confirm field mapping through the interface, and proceed. Data problems are flagged during validation rather than requiring pre-formatting. For teams with established account lists they’ve maintained in Excel for years (and there are many), this approach is far less disruptive.

The right choice depends on your situation. If you’re doing a one-time migration of your customer book into Paxelo, flexible mapping with a test batch is the way to go. If you’re refreshing account data monthly from CRM exports, a saved mapping template speeds up repeat imports significantly.

Importing From a CRM Export

Many outside sales teams start by exporting their account list from Salesforce, HubSpot, or another CRM and importing it into Paxelo for routing and territory management. A few tips specific to CRM exports:

• Export only active accounts. Closed/lost accounts and duplicates in your CRM will carry over into your route planner unless you filter them out first.
• Map CRM fields to Paxelo fields deliberately. Your CRM’s “Account Owner” might map to Paxelo’s Territory Assignment. “Annual Contract Value” might map to Revenue. Think about which CRM fields drive routing and territory decisions.
• Add priority tiers before import if your CRM doesn’t have them. Many CRMs track revenue and activity but don’t have an explicit A/B/C tier field. Add a column to your export and classify accounts before uploading to Paxelo.
• Plan for ongoing updates. Until Paxelo’s Salesforce and HubSpot integrations launch (currently on the roadmap), periodic CSV re-imports are how you keep account data current. Using a consistent account ID field makes re-imports update existing records rather than creating duplicates.

Frequently Asked Questions

What file format should I use to import a spreadsheet into Paxelo?

CSV is the most universally compatible format. It avoids issues with macros, formulas, and encoding that can affect XLS and XLSX files. If your data includes special characters or accented names, make sure the CSV is saved with UTF-8 encoding.

What is field mapping during a spreadsheet import?

Field mapping is the process of matching each column in your spreadsheet to a corresponding data field in Paxelo. For example, your “Company Name” column maps to the Account Name field, and “Priority (A/B/C)” maps to Account Priority Tier. Some columns are auto-mapped; others require manual selection from a dropdown.

How many accounts can I import at once?

Some platforms recommend no more than 3,000 contacts per batch. Paxelo’s free plan supports up to 50 customers, which is enough to test the import process. Paid plans support larger account lists. When in doubt, start with a smaller batch to validate before running the full import.

How do I include account priority and visit frequency in my import?

Add columns for Priority (with consistent values like A, B, C) and Visit Frequency (with values like Weekly, Biweekly, Monthly). These fields feed Paxelo’s automatic schedule generation and revenue-optimized routing. Without them, the system can’t differentiate between your most valuable accounts and the rest.

Why did my spreadsheet import fail?

The most common causes are macros or formulas in cells, missing column headers, special characters in address or company name fields, multi-tab workbooks where the wrong sheet was selected, and CSV files that weren’t properly delimited. Strip formulas, clean headers, and save as a fresh CSV to resolve most failures.

Can I import a spreadsheet from Google Sheets?

Yes, but you’ll need to first export the Google Sheet as a CSV or XLSX file (File > Download > Comma-separated values). Direct Google Sheets integration isn’t available in most route planners today.

How do I avoid creating duplicate accounts during import?

Check your source file for duplicates before importing. Use a unique identifier column (like account ID, CRM record number, or email address) so the tool can match against existing records. Many platforms include a duplicate detection step during validation.

What’s the difference between importing a spreadsheet and syncing with a CRM?

Importing is a one-time (or periodic) push of data from a file into Paxelo. Syncing is an ongoing, typically bidirectional connection that keeps records current in both systems automatically. Paxelo’s CRM integrations (Salesforce, HubSpot) are on the roadmap. In the meantime, periodic CSV imports are how teams keep account data fresh.

Can I assign accounts to territories during import?

Yes. Include a Territory column in your spreadsheet with consistent territory names or codes. During field mapping, match this column to Paxelo’s territory assignment field. After import, accounts appear on the correct territory maps and in the right rep’s coverage analytics.

How do I update existing account data without creating duplicates?

Use a unique account identifier (like an account ID or CRM record number) in your spreadsheet. When re-importing, Paxelo can match incoming rows against existing records using that identifier and update fields rather than creating new entries. This is especially important for teams doing monthly CRM refreshes.

Ready to get your account list out of the spreadsheet and into a system that turns it into prioritized routes and territory coverage maps? Paxelo lets you import your customer book and start building revenue-optimized routes in minutes. Start free with up to 50 accounts (no credit card needed) or book a demo to see how it works for your team.