Moving from spreadsheets to business software: migrating your customer list and records

How do you know you've outgrown the spreadsheet?

Excel isn't a bad tool, but used as a business system it shows these signs:

• Copies of the same file called "final", "final-2", "really-final".
• When two people edit at once, one overwrites the other.
• Customers, bookings and payments are in separate files; updating one leaves the others stale.
• Nobody knows who changed which row.
• The file is hard to open on a phone; the field team can't use it.
• Reminders, notifications and reports all need manual work every time.

If three of these sound familiar, it's time. The good news: the data you kept in spreadsheets is the most valuable material for the move.

Step 1: Decide what to move

You don't have to move everything. Start with an inventory:

Rule: move what you need to run the future; archive the past. Moving five years of past bookings row by row is usually unnecessary; the customer's last visit date and important notes are enough.

Step 2: Clean the data

Cleaning is the longest step and the most important. Dirty data stays dirty in the new system.

Phone numbers

The same number may appear as "0532 123 45 67", "5321234567" and "+90 532 123 4567". Bring them all to one format; the international format (starting with the country code, such as +90) is safest. WhatsApp and SMS sending expect it too.

Names

"AYŞE YILMAZ", "ayşe yılmaz" and "Yılmaz Ayşe" may be one person. Split first and last names into separate columns and fix capitalisation.

Duplicates

The same customer may be on several rows. Sort by phone and email and merge matches. Don't lose notes when merging; combine notes from both rows into one.

Empty and meaningless values

Clear values like "-", "none" and "?". Put dates in one format. Remove currency symbols and thousand separators from amounts, leaving only the number.

Step 3: Map the columns

The new system expects certain fields for each record type. Map your spreadsheet columns to them:

For columns without a match there are two options: define them as extra fields in the new system, or merge them into the note field. Making every column an extra field complicates the new system; pick the fields you will really use.

Step 4: A small test first

Before importing the whole list, test with 20–30 rows. Afterwards, check:

• Do special characters (such as ı, ş, ğ, ü, ö, ç) display correctly? If not, save the file as UTF-8.
• Are dates on the right day and month? Day and month may have swapped.
• Are phone numbers in the right format?
• Did duplicates appear?

If the test is clean, import the rest.

Step 5: Opening balances

Rather than moving open debts, remaining instalments or remaining pack sessions as historical transactions, enter them as opening balances. "This customer owed 4,500 as of 1 November, with two instalments left on 15 November and 15 December" is enough.

Step 6: Bring the team across

Most software changes fail not for technical reasons but because people carry on with old habits.

1. 01
   Set a switch date. After it, new records go only into the new system.
2. 02
   Make the spreadsheet read-only. Old files can be opened as an archive but not edited.
3. 03
   A short session per role: how does reception see bookings, the till see payments, the manager see reports?
4. 04
   A short daily check for the first two weeks: what couldn't they find, what did they find hard?
5. 05
   Everyone gets their own account. A shared password carries the spreadsheet's "who changed this?" problem into the new system.

Step 7: What to do with the old files

The archived files contain personal data. Don't leave them indefinitely in a folder everyone can reach. Set a retention period, restrict access and destroy what's past it, as data protection laws such as GDPR and Turkey's KVKK expect.

Example: a dietitian's office moves over

Picture an office with two dietitians. Clients are in an Excel file, bookings in Google Calendar, payments in a separate file, and measurements (weight, body fat) on a separate tab per client.

Inventory: four files, 380 clients, 46 tabs of measurements. Decision: move the client list, upcoming bookings, open balances and the last three months of measurements; older measurements stay in the archive.

Cleaning: 70 phone numbers are in different formats; all are converted to international format. 24 clients appear twice and are merged. Some clients have only a first name; last names are filled in from the payments file.

Mapping: name, phone, email and notes go to the customer record; measurements go to a measurements table linked to the client, with date, weight, body fat and waist fields.

Test: the first 25 rows are imported; day and month have swapped in the dates. The file is re-saved with the date format fixed; the second test is clean.

Switch: Monday is announced as the switch date. From then on, new bookings and measurements go only into the new system; old files move to a read-only archive folder, accessible only to the two dietitians.

First two weeks: the dietitians find entering measurements slow; the measurement form is simplified so it can be filled in on a tablet during the consultation.

The whole move takes a few days, most of it cleaning. The payoff shows in the first month: each client's whole history on one screen, booking reminders going out by themselves, and "did this client owe us anything?" answered at a glance.

Moving to Era

In Era each customer has one Customers record that every module uses; duplicates can be merged later too, and several ways of recognising someone (phone, email) live on one record. Your service and product list goes into the Catalog, upcoming bookings are imported into Appointments, and open balances and instalments open as agreements and instalments in Finance. Your team lives in the Team module.

For lists you kept in spreadsheets that don't fit any module, there is the Tables module: create your own tables and fields, import and export records, link tables to each other, add formula and summary fields, and decide who may see which table and which rows. Extra fields can also be added to existing module records.

In chat, Era helps: share the file and ask "which Era fields do these columns map to, and what needs cleaning?", and work out the import plan together. Era does this with your permissions and the AI source you connected. Your data can always be exported; if you leave Era, your customer list and tables come with you.

Checklist

1. 01
   Files to move and files to archive are decided.
2. 02
   A backup copy sits in a separate folder.
3. 03
   Phone, name, date and amount formats are clean.
4. 04
   Duplicates are merged.
5. 05
   Columns are mapped to fields.
6. 06
   A 20–30 row test was run.
7. 07
   Opening balances are entered.
8. 08
   The switch date is announced; the spreadsheet is read-only.
9. 09
   Everyone has their own account.