This guide provides essential best practices for preparing and importing data into your Pulse system. Following these guidelines will help prevent common import errors and ensure smooth data migration.
Prepare Your CSV File Using Microsoft Excel
Always open and verify your CSV file in Microsoft Excel, even if it was created in another tool. Excel provides stronger control over data formatting, validation, and error detection.
Avoid using Google Sheets to prepare CSV files, as it may introduce formatting issues (such as incorrect decimals or number formatting) when saving as CSV.
Pricing & Numeric Field Formatting
Price Field Best Practice
Remove all dollar signs ($) from pricing data and it is recommended that all price values include two decimal places (e.g., 5.00 instead of 5 or 5.5). This ensures consistency and accuracy across systems.
- Format pricing fields as "Number" in Excel, NOT "Currency"
Numeric Field Formatting
Ensuring proper numeric formatting is critical for consistency, accurate reporting, and error-free data imports:
- In Excel, commas in numeric fields only function correctly if the column is formatted as Number
- For smoother CSV imports, it is best to avoid commas in amount values
- Remove spaces and special characters from numeric fields
Systematic Troubleshooting Approach
Template-Based Import
Always start with the system's exported CSV as your template—never create import files from scratch. This ensures proper column structure and formatting.
Comparison Method
Follow these steps to ensure your import file matches the system's requirements:
- Export a sample CSV from your Pulse system
- Compare the exported CSV format against your import file and legend
- Identify any discrepancies in formatting, column order, or data structure
- Adjust your import file to match the exported template exactly
Incremental Testing Strategy
Use this approach to isolate problematic data and identify exactly where formatting issues exist:
- Test with 1 row: Import only 1 data row to verify basic formatting
- Test with 10 rows: If successful, import the first 10 rows
- Test with 100 rows: If successful, import the next 100 rows
- Test in batches of 500: Continue with batches of 500 rows until you identify any rows with formatting issues
Import Type Selection
Before importing, carefully verify the following:
- Verify you're selecting the correct import type for your data (products, customers, inventory, etc.)
- Review the import mapping screen carefully
- Double-check before clicking Process or Import
File Naming Conventions
Follow these naming best practices to avoid file processing issues:
- Avoid spaces and special characters in file names
- Keep file names concise and descriptive
- Use underscores or hyphens instead of spaces
Examples:
- ✅ Correct: product_import_2026.csv, customer-data-jan.csv
- ❌ Incorrect: Product Import 2026.csv, customer data (jan).csv
Additional Best Practices
Before importing, always verify the following:
- All required fields are populated
- Column headers remain unchanged and in the correct order
- No hidden characters or extra spaces exist in cells (use Excel's TRIM() function if needed)
- Your original file is backed up before making formatting changes
Common Causes of Import Errors
If an import fails or results in a blank screen with no error message, check for:
- Inconsistent formatting across rows or columns
- Special characters or formatting in numeric fields
- Incorrect file encoding (CSV files should be UTF-8)
- Missing required fields
- Data shifted into incorrect columns due to mapping issues
Quick Pre-Import Checklist
Taking a few extra minutes to validate formatting, test incrementally, and follow system templates can save hours of troubleshooting later. Consistency and simplicity are key to successful data imports.
Before clicking Import, verify:
- File opened and verified in Microsoft Excel
- Using system's exported CSV as template
- All pricing fields include exactly 2 decimal places
- All numeric fields formatted as "Number" without special characters
- Column headers match the exported template exactly
- No spaces or special characters in file name
- All required fields are populated
- Backup copy of original file created
- Correct import type selected
- Import mapping verified before processing