# Moving from Excel to a CRM: migration checklist | Corex360 > How do you move an Excel customer list into a CRM? Map the columns, remove duplicates, fix phone formats, assign owners, and retire the old file last. Source: https://www.corex360.com/en/blog/crm-migration-checklist Last updated: 2026-09-29 --- ![A cardboard box with a string-tied stack of papers by a window, next to a row of pink and blue binders] CRM # CRM migration checklist: moving from Excel step by step A CRM migration checklist is a list that writes down in advance how the Excel customer list is cleaned, how columns map to fields, how phone and date formats are unified, how the team is prepared, and when the old file closes. [Request a demo](https://www.corex360.com/en/contact?konu=crm#form) [Corex360](https://www.corex360.com/en) [Blog](https://www.corex360.com/en/blog) CRM migration checklist: moving from Excel step by step Contents - 01 What needs checking before the move? - 02 How do you move an Excel customer list into a CRM, step by step? - 03 Switch all at once, or in phases? - 04 Which route suits which company? - 05 What needs attention during the move? - 06 What should you check after the move? - 07 How does a move to Corex360 work, and where are its limits? Ş **[Şevket Erer](https://www.corex360.com/en/blog#blog-hakkinda)** Co-founder, AI Specialist · Corex360 24 September 2026 7 min read [Modules](https://www.corex360.com/en/modules) [Solutions](https://www.corex360.com/en/solutions) A CRM migration checklist is a list that writes down in advance what will be cleaned, what will be mapped, how the team will be prepared, and on which day the old tool will be retired when customer data moves from old files into the new system. The hard part of a migration is not moving the data but getting the team to start writing to the new record. The list is written for teams that have decided to move and keep customer details in Excel today; whichever CRM you choose, preparing the file is the same. ** 01. ## What needs checking before the move? ** Short answer Before moving to a CRM, write down where customer data lives, which source wins when they disagree, who owns it, and which fields will be carried over. Example scenario: Picture a crop protection distributor in Adana. Customer details sit in the sales manager's Excel file, in the field reps' phone contacts, in accounting's customer account list, and in an old email inbox. The same cooperative is recorded under a different spelling in each. - List every place customer data lives: spreadsheets, phone contacts, email inboxes, and the customer account list in accounting. - Give each source an owner, and write down which source wins when they disagree. - Weed out duplicate records for the same customer, matching on company name, tax number, phone, and email. - Choose the fields to carry over, and leave behind the columns nobody fills in. - Check that your privacy notice is up to date. - Put in the calendar the day the old file becomes read-only. At the Adana distributor, drawing up this list also opens the debate over which source counts as correct: the field rep's contacts might win for phone numbers, and accounting's customer account list for company names and tax numbers. Writing this decision down before the move heads off the argument that would follow the import. Cleaning is also easier before the move, in the old file; skip it and the team meets duplicate cards in the first week and loses faith in the new system. ** 02. ## How do you move an Excel customer list into a CRM, step by step? ** Short answer Before an Excel list goes into a CRM, it is cleaned and brought into one format. It is copied, details are split into their own columns, phone and date formats are unified, duplicates are removed, every row gets an owner, and a small part is tried first. Which file formats a CRM accepts, and how columns map to fields, varies from one CRM to the next. The preparation steps are about the file itself, so they help whichever system you move to. At the Adana distributor, the sales manager's Excel file was chosen as the master list, details from the other sources were carried into it, and the preparation was done on that file. You can download an empty template with the same eight columns as an [Excel file](https://www.corex360.com/v2/indir/crm-migration-template.xlsx) or a [UTF-8 CSV file](https://www.corex360.com/v2/indir/crm-migration-template.csv); it contains no data. - Make a copy: leave the original file untouched, do all the work on a copy, and note the day the copy was made. - Keep a single header row: remove merged cells, subtotals, and empty rows. Meaning carried by colour is lost in the import; write that meaning into a column. - Give each detail its own column: company name, contact person, phone, email, and city should not share a cell. If a cell holds two phone numbers, move the second to its own column. - Unify the phone format: keep numbers in text-formatted cells and in one way of writing. A number stored as a numeric value loses its leading zero. - Bring dates into one format: write every date column the same way so day and month are not swapped, and fix dates left as text. - Remove duplicate rows: match the same company on name, tax number, phone, and email, and decide which row stays by your source rule. - Add an owner column: write the name of the person responsible for each customer on every row. A row with no owner still belongs to nobody after the import. - Separate stage and next step: put the customer's stage and the date of the next task in their own columns, and have everyone use the same words for stages. - Protect Turkish characters: if the system asks for a CSV file, save it with UTF-8 encoding; otherwise letters such as ğ, ş, and ı can come out garbled. - Run a small trial first: import a small part of the list, open a few cards and compare them with the old rows, and move to the full list once nothing is off. From Excel column to CRM field | Column in Excel | Field in the CRM | Common import problem | |---|---|---| | Company or registered name | Customer (company) record | Different spellings of one company open separate cards | | Contact person | Contact | More than one name in a single cell | | Phone | The contact's or company's phone | Leading zero dropped, inconsistent formats | | Email | The contact's email | Two addresses in one cell, stray spaces, typos | | Last contact note | Note on the card | The note has no date | | Status | Opportunity stage | Different words for the same stage | | Follow-up date | Task date | Day and month swapped | | Owner | Record owner | Rows left blank | At the Adana distributor, the job that takes longest would most likely be the status column: some will have written 'spoke to them' and others 'waiting on quote' for the same stage. Before the import, the team agrees on a few shared stage names and converts the old words into them. If that decision is skipped in the file, the first week in the CRM shows the same work sitting at two different stages. ** 03. ## Switch all at once, or in phases? ** Short answer Switching all at once leaves no limbo between old and new but needs thorough preparation; a phased move splits the risk but lengthens the time two systems live side by side. - Preparation: when switching all at once, data, fields, and users must be ready from day one. In a phased move each phase is prepared separately and the first round is lighter. - Risk: when switching all at once, a mistake hits everyone at the same moment. In a phased move a mistake shows up in the first team or the first workflow and gets fixed. - Duplicate records: when switching all at once, the old file closes on day one. In a phased move two places are updated for a while, and the question of which one is right can arise. - Learning: when switching all at once, the whole team learns at the same time and support requests peak in the same days. In a phased move the first team sets the example for the others. - Duration: switching all at once finishes on a shorter timeline. A phased move takes longer but brings feedback at the end of each phase. The choice depends on how far preparation has gone. If data, fields, and users are ready from day one, a single cutover keeps the calendar short and the old file closes on the first day. If preparation moves piece by piece, a phased move shows errors in the first team, where they are fixed, and that team becomes an example for the others. If you choose the phased route, write down at the start which record counts as the master while both places are being updated. ** 04. ## Which route suits which company? ** Short answer If the team is small, data comes from one source, and the process is simple, switch all at once; if there are several teams, branches, or data sources, a phased move is safer. For the Adana distributor a phased move makes more sense: first the sales team at head office starts quote follow-up in the CRM, the field reps move to the mobile app a few weeks later, and the accounting team joins last. At each phase the old method closes only for that team. For a small team selling from a single showroom, splitting into phases just drags things out. The old file closes on a Friday evening, everyone works from the new card on Monday, and one person is set aside to answer questions in the first week. Whichever route you take, starting with a single workflow makes the move easier; in most companies that is quote follow-up. ** 05. ## What needs attention during the move? ** Short answer During a CRM move, imported data should be spot-checked, permissions should be given by role, and every user should try things out with one of their own customers. - After the import, open the cards of a few customers you know well and compare the fields with the old source. - Give permissions by role rather than by person, and write down who sees which records. - On the first day, have every rep open one of their own customers' cards and enter a note and a task. - Check that WhatsApp, email, and phone channels are connected to the card. - Set up one place to collect questions and one person responsible for them. Spot checks catch on the first day what slipped through the file preparation: a swapped date, a garbled letter, a dropped zero. A mistake found in the first week is fixed before the team loses faith in the new system. Whether WhatsApp, email, and phone channels are linked to the card also shows on a familiar customer's card; collecting questions in one place with one owner makes it clear who handles these fixes. ** 06. ## What should you check after the move? ** Short answer After moving to a CRM, check that the old file has really closed, that cards are kept up to date, and that the manager reads the state of things from the new system. - Did the old file become read-only on the day in the calendar? - Are new customers going onto cards, or still into a spreadsheet? - Are quotes prepared on the card, with the next step's date filled in? - Does the manager open the screen in the weekly meeting, or ask for a separate report? - Has access been updated for people who left or changed roles? The manager question is a subtle sign. If the manager still asks for a separate Excel report, the team keeps writing in two places and the move stays half done. Repeat this check every week in the first weeks after the move; the move is finished when every question is answered yes. Access for people who leave or change roles is part of this weekly check too. ** 07. ## How does a move to Corex360 work, and where are its limits? ** Short answer When moving to Corex360, existing customer and contact records are migrated together with you. A checklist does not solve everything. The aim of the move is to keep the record in one place from tomorrow on; some of the old conversations left on phones and in personal inboxes may stay in the past. You can see how the customer card opened from the moved records is laid out on the [Corex360 CRM module](https://www.corex360.com/en/modules/crm) page. If you have not yet decided whether to move, start with [Excel or a CRM](https://www.corex360.com/en/blog/excel-or-crm); if you are still choosing a CRM, see [how to choose a CRM](https://www.corex360.com/en/blog/how-to-choose-crm). In the demo you see how the card would look with your own customer records and agree the scope of the import together. ## Sources - [Personal Data Protection Authority, Obligation to inform (Law No. 6698)](https://www.kvkk.gov.tr/Icerik/2033/Aydinlatma-Yukumlulugu-) Last checked 24 September 2026 - [Personal Data Protection Authority, Data security obligations (Law No. 6698, Art. 12)](https://www.kvkk.gov.tr/Icerik/2040/Veri-Guvenligine-Iliskin-Yukumlulukler) Last checked 24 September 2026 ## How was this page prepared? - Written by: [Şevket Erer](https://www.corex360.com/en/blog#blog-hakkinda), Co-founder, AI Specialist - Sources: legislation, official body, and vendor information is taken from the primary sources in the Sources list on this page; each source shows the date it was last checked. - Product information: sentences about Corex360 rest on the company's product fact records; unconfirmed features are not written. - Use of AI: the Corex360 team writes the text; AI tools are used for drafting and translation. [Publishing principles](https://www.corex360.com/en/about#yayin-ilkeleri) - Dates: first published 24 September 2026 . [Corrections policy](https://www.corex360.com/en/about#duzeltmeler) ## Frequently asked ** 01 What is a CRM migration checklist? ** A CRM migration checklist is a list that writes down in advance the jobs involved in moving customer data from old sources into the new system, such as cleaning, field mapping, permissions, team preparation, and retiring the old file. Its purpose is to follow the move past the import day, up to the point where the team starts writing to the new record. ** 02 How long does a move to a CRM take? ** It depends on how scattered the data is, how the teams and branches are organised, and which route you choose. With a single, clean customer list the move is short; if sources are scattered, cleaning can take longer than the move itself. ** 03 Which data should not be carried over to a CRM? ** Records with no activity for years, personal data whose purpose has lapsed, and old notes nobody trusts should be left behind. Before deleting anything you do not carry over, check your retention obligations. ** 04 Should selling stop during the move? ** No. Choose a time away from busy days such as period end and closing weeks. When switching all at once, leave no gap between the day the old file closes and the day the new card opens. ** 05 What should be done if the team does not use the new CRM? ** First ask why: the usual answer is too many required fields, a missing channel, or an old file still open. Cut back the required fields and close the old file. ** 06 Should the customer account list in accounting move into the CRM? ** The customer's master record should live in one place. Write down at the start which system counts as correct for which field: contact details and sales history in one place, while how account balances are followed is decided by your accounting setup. ✳ **See the customer card with your own data** Quotes, Contracts, Projects, and Finance are tabs on the same customer card; let us open one of your own customers on that card together. [Request a demo](https://www.corex360.com/en/contact?konu=crm#form)[WhatsApp](https://wa.me/905321323288)[CRM](https://www.corex360.com/en/modules/crm) Related articles ## Keep reading. [Back to the blog](https://www.corex360.com/en/blog) [CRM What is CRM? What an SME sales team expects from it CRM is software that keeps the customer relationship on one record. In an SME sales day, the customer card, opportunities, quotes, and follow-up work together. Date 23 September 2026 Read the article 01](https://www.corex360.com/en/blog/what-is-crm)[CRM Customer tracking in Excel or a CRM: which one, and when When is Excel enough for tracking customers, and when is it time for a CRM? Weigh the criteria, see the limits of each, and spot the signs early. Date 24 September 2026 Read the article 02](https://www.corex360.com/en/blog/excel-or-crm)[CRM CRM data migration: exporting, mapping fields, and running both systems for a while Switching CRM means taking a full export from the old system, mapping its fields to the new one, and running both side by side for a short, planned period. Date 25 September 2026 Read the article 03](https://www.corex360.com/en/blog/switching-crm-moving-your-data)[CRM What is mobile CRM, and what should the phone in the field show Mobile CRM opens the customer card, tasks, and approvals on a phone, so the field sees the office record. What to show, app or site, offline, and security. Date 28 September 2026 Read the article 04](https://www.corex360.com/en/blog/what-is-mobile-crm)[CRM How to choose a CRM: cloud, own server, one core Choosing a CRM starts with where you lose customers, not a feature list. A feature you never try with your own card in the demo will not help after setup. Date 23 September 2026 Read the article 05](https://www.corex360.com/en/blog/how-to-choose-crm)[CRM What drives CRM cost: the decisions behind the price table CRM cost is shaped by users, module scope, hosting, data migration, integrations, setup, and training. Ask the vendor about each of these items separately. Date 23 September 2026 Read the article 06](https://www.corex360.com/en/blog/what-drives-crm-cost)[CRM What is lead scoring: which prospect to call back first Lead scoring rates prospects against your own criteria and ranks whom to call back first. The criteria, building a model, common errors, and data law. Date 28 September 2026 Read the article 07](https://www.corex360.com/en/blog/what-is-lead-scoring)[CRM How to track sales: from opportunity to quote, and from quote to contract Sales tracking keeps each opportunity's source, stage, and next step on record. What the card holds, how to spot a stalled deal, and why losses are logged. Date 24 September 2026 Read the article 08](https://www.corex360.com/en/blog/how-to-track-sales) Was this page useful?