Migrating Customer Data to a New System SA
Fear of data migration stops many SA distributors switching software. Learn what customer data migration actually involves and how to do it cleanly.
Table of Contents
The Fear That Keeps Businesses on Bad Systems
Ask a sales manager why their company is still running on a patchwork of spreadsheets and WhatsApp messages despite knowing better options exist, and "we can't face moving all the data" comes up more often than any other reason. Data migration anxiety is real — and it keeps South African distribution businesses stuck on systems that cost them money every day.
The anxiety isn't irrational. Customer data is the lifeblood of a distribution business. Losing it, corrupting it, or getting it wrong during a system transition is genuinely catastrophic. But the fear is usually disproportionate to the actual difficulty — especially when you know exactly what you're dealing with before you start.
Migration is simpler than you think. Start your 14-day free trial and import your customer data from a spreadsheet — our import tool handles the heavy lifting. No credit card required.
What "Customer Data" Actually Contains
Before you can plan a migration, you need to understand what you're migrating. Customer data in a distribution context typically includes:
- Identity: Business name, trading name, registration number, VAT number
- Location: Physical address (delivery), postal address (invoicing), GPS coordinates if available
- Contacts: Primary buyer name, mobile number, email address, secondary contacts
- Commercial terms: Account number, credit limit, payment terms (30 days, 60 days, COD), assigned price list
- Operational data: Assigned sales rep, territory, visit frequency, preferred delivery days
- History: Order history, visit records, account notes
Not all of this needs to move on day one. A practical migration prioritises the data that reps need at the point of sale: customer identity, contacts, location, price list assignment, and account terms. Historical order data can be migrated separately or archived rather than migrated.
Common Data Quality Problems in SA Distribution
Here's what actually makes migrations hard — not the volume of records, but the quality of what's in them. Years of informal data entry accumulate problems that need to be resolved before importing:
Duplicate Entries
The same customer appears twice under slightly different names: "ABC Stores (Pty) Ltd" and "ABC Stores Pty Ltd". Or the same customer has been entered separately for their main branch in Johannesburg and their Cape Town branch — when they should be branches under a single parent account. Importing duplicates creates data integrity problems that are harder to fix after migration than before.
Address Problems
Delivery addresses entered in free-text fields with no structure. "Behind the Spar, next to the Engen" is not a deliverable address. Physical addresses in the postal address field and vice versa. GPS coordinates from years ago before a customer moved premises.
Contact Field Misuse
Mobile numbers entered in the landline field. Email addresses in the notes field. Multiple contacts all entered in a single "contact" field separated by commas or slashes. Primary contact who left the business two years ago still listed as the main contact.
Missing VAT Numbers
A significant issue for B2B trading in South Africa, where VAT compliance is non-negotiable. Customers registered for VAT without their VAT number on the account create problems at invoicing. This needs to be resolved before migration, not after.
Naming Convention Inconsistencies
"(Pty) Ltd" vs "Pty Ltd" vs "(PTY) LTD" vs "Proprietary Limited". Account names that have changed after acquisitions. Abbreviated names used inconsistently. These inconsistencies cause headaches in deduplication and in matching the migrated data to existing financial system records.
The Spreadsheet Import Approach
The most practical path for most SA distributors is migrating via structured spreadsheet import. This means:
- Export your current data — from whatever system or files you're currently using, into a spreadsheet format (CSV or Excel)
- Clean the data — resolve the issues described above before importing
- Map the columns — tell the new system which of your spreadsheet columns corresponds to which field in the system
- Import and review — bring the data in, then audit a sample for accuracy
The column mapping step deserves specific attention. Your spreadsheet probably has columns named things like "Customer Name", "Tel", "Rep", "Price Group" — while the system you're migrating to has fields named differently. A good import tool allows you to drag-and-drop your column names onto the destination fields, handling non-standard naming without requiring you to rename your entire spreadsheet. The spreadsheet import feature is designed specifically for this kind of flexible mapping.
Clean in Excel first, then import. Our spreadsheet import tool maps your columns to the system's fields — no rebuilding from scratch. Start your free trial and bring your customer data across today.
Deduplication: The Most Important Pre-Migration Step
Before importing, run a deduplication check on your customer list. The simplest approach:
- Sort by customer name and scan for obvious duplicates
- Sort by phone number and look for the same number appearing multiple times under different names
- Sort by VAT number to catch the same legal entity under different names
- Look for address duplicates — same street address under different account names
For large customer lists (1,000+ records), a formula-based fuzzy match in Excel can automate the identification of near-duplicates. Most spreadsheet tools can do this with VLOOKUP or a dedicated deduplication add-in.
Grouping Customer Branches Under Parent Accounts
A common structure in SA distribution is a retail chain with multiple branches, each of which orders independently but sits under a single parent account for credit limit purposes. During migration, you need to decide:
- Which accounts are standalone? — independent retailers with no branch relationship
- Which are parent-child? — chain stores where individual branches order but credit is managed centrally
- Which are linked branches? — same business, different physical locations, same trading terms
Setting this up correctly at migration time prevents confusion later when credit limits, consolidated statements, or account-level reporting comes into play.
Realistic Migration Timelines
How long does customer data migration actually take? Based on typical SA distribution businesses:
| Customer Count | Typical Migration Time |
|---|---|
| Up to 500 | 1-2 days (data cleaning + import) |
| 500-1,000 | 2-4 days |
| 1,000-5,000 | 1-2 weeks |
| 5,000+ | 2-4 weeks (phased approach recommended) |
These estimates assume data that is reasonably well-organised to begin with. Businesses with particularly messy historical data should add 50-100% to the cleaning phase.
What to Do with Incomplete Records
Not every customer record will be complete. You have two options:
- Import with gaps — bring in what you have, flag incomplete records for follow-up, and let reps complete the data during their next visit
- Clean first, then import — delay the migration until all records meet a minimum completeness standard
For operational data like contact numbers and addresses, the second approach is preferable. For administrative data like VAT numbers that can be collected over time, importing with gaps and a flag for follow-up is practical.
Testing After Migration: Verifying Accuracy
A sample audit is essential after any migration. Select 20-30 customer records at random — ideally weighted toward your highest-value accounts — and manually verify:
- Does the name match what's in your previous system exactly?
- Is the address correct and deliverable?
- Is the assigned rep correct?
- Is the price list assignment right?
- Is the VAT number present and in the correct format?
If the sample shows error rates above 5%, investigate whether the problem is systemic (a column mapping error that affected all records) or random (spot data quality issues). Systemic errors need to be corrected in bulk; random errors can be corrected individually.
After Migration: The Ongoing Discipline
Migration is not a one-time project — it's the start of a data governance practice. Once your data is clean and in a proper system, keep it clean:
- Establish a standard for how new customers are added (who does it, what fields are required)
- Review for duplicates quarterly
- Update inactive accounts rather than creating new ones for customers who return after a gap
- Train reps to update contact information in the field, not on paper that gets lost
Clean master data is a competitive asset. South African distributors who know their customer base accurately — right addresses, right contacts, right terms — deliver better service and waste less time on preventable errors.
Start your 14-day free trial and bring your customer data across using our spreadsheet import tool — we'll help you map the columns and get your team operational quickly.
Related Articles
Ultimate Guide to Stock Management Systems for South African Businesses
Complete guide to choosing the perfect stock management system for your South African business. Compare features, pricing, and implementation strategies for optimal inventory control.
Sales Rep Software Comparison: Top 10 Solutions for 2025
Compare the top 10 sales rep software solutions for 2025. Detailed analysis of features, pricing, and capabilities to help you choose the perfect sales management platform.
Commission Calculation Made Simple: Tools & Best Practices
Master commission calculation with our comprehensive guide. Learn formulas, tools, best practices, and common structures to optimize your sales compensation strategy.
Ready to Transform Your Sales Operations?
Discover how SalesPro Hub can help you implement the strategies discussed in this article and take your sales performance to the next level.