--- title: "Consolidating three systems into one, step by step | attendo" description: "How to bring support, maintenance, field service and CRM onto one platform in phases: where to start, running old and new together and what not to migrate." url: "https://attendo.me/en/blog/from-three-systems-to-one" lang: "en" --- # How to go from three systems to one without stopping operations The idea is appealing and the fear is reasonable: replacing the systems your company runs on sounds like weeks of chaos. It can be done without anyone noticing, but not all at once. - By the attendo team - Published September 27, 2026 - 4 min read **In this article** 1. The decision that shapes everything: where you start 2. The coexistence rule 3. Phase by phase 4. How to import without duplicates 5. What almost always goes wrong 6. What not to migrate 7. How to know it worked ## The decision that shapes everything: where you start Do not start with the system that hurts most. Start with the one that has **the fewest dependencies**. | If you start with… | Advantage | Risk | | --- | --- | --- | | Maintenance | A contained area, few people and visible results in a month | Low | | Support | It comes in through channels and connects easily | Medium: it is your face to the customer | | Sales | Few people | Low, but it adds little at first | | Connecting the ERP | None as a starting point | High: never first | An order that tends to work: maintenance, field service, support, sales and, last, the connection with the ERP that does your invoicing. Each phase feeds the next, and billable work reaches the ERP when the data it depends on is already reliable. ## The coexistence rule During the transition you will have two live systems. The rule that prevents disaster: **each piece of data has one system in charge of it**. If customers are created in the new system, they are created only there, and synced to the old one. Never in both. The day someone creates a customer in both places, the records start to drift apart, and that never gets fixed. ## Phase by phase ### Phase 0. Inventory of the truth (one week) A list of which data lives in which system and which system is in charge of it. It is boring and essential, and it is where the surprises appear: the three systems usually have different customer lists. ### Phase 1. First module (three or four weeks) Set it up with real data, test it with a small team and switch over. A module left half-done indefinitely is the worst thing that can happen. ### Phase 2. Second module (three or four weeks) This is where the first real benefit shows up: two areas sharing the same customer record. ### Phase 3. Channels Email, WhatsApp and phone move to the new system. It is the point of no return, and it is best done when the team is already comfortable. ### Phase 4. Connecting the ERP Last. Invoicing and accounting stay in your ERP: what changes is that billable work reaches it without retyping. By then, hours and parts are coming in properly, and that is what makes the invoice reliable. ## How to import without duplicates 1. Export what is there first, as a backup. 2. **Do a dry run.** Validate the whole file without saving anything, and read what it would create, what it would update and what would fail. 3. Test the real import with ten rows and check the result by hand. 4. Import the rest and fix only the rows that fail, not the whole file. 5. Pick a code that identifies each record, such as each customer’s tax ID, and never change it. With it, you can repeat the import without creating duplicates. And if you only need to fix one field, such as the account owner of each customer, you do not need to reimport everything: upload the code and that one column. ## What almost always goes wrong **1. Duplicates show up in phase 0 and nobody wants to decide.** Three customer lists with different names for the same company. Someone has to decide which one wins and clean it up, and they need the authority to do it. **2. Someone keeps using the old system.** There is always someone who finds it “handier there.” If you do not truly switch off, they contaminate the data for months. **3. The old system gets copied as it is.** Flaws and never-used fields included. Migration is your only chance to clean up, and wasting it is expensive. **4. People outside the project are not trained.** The pilot team knows everything, and everyone else finds out on the Monday it goes live. ## What not to migrate - **History older than 24 months.** It slows things down, adds clutter and nobody looks at it. If needed, keep an export. - **Fields nobody fills in.** If 90% of a field is empty in the old system, leave it behind. - **Settings for a process that no longer exists.** Ask “why is this here?” If the answer is “I don’t know,” do not migrate it. Calculator Run the numbers with your own data Return ### [attendo ROI](https://attendo.me/en/calculators/roi) The hours and money your team gets back when it stops hunting for data, retyping service reports and chasing approvals. ## How to know it worked Three months after the last switch-over: nobody opens the old system, no data is typed twice and the reports that used to be built by hand simply open. It is not a weekend project, and it is not a year-long one either. It is four or five phases of a few weeks, each ending with a real switch-over. And phase 0, the boring one, decides whether it works. Last updated: October 6, 2026 Downloadable guide · Checklist Business software implementation checklist What you want done before, during and after switching business software, in lists you can tick off: the data to prepare, how to migrate without duplicates, how to train each role and what to measure in the first weeks. [Download the free guide](https://attendo.me/en/guides/software-implementation-checklist) ## How attendo handles it attendo brings support, maintenance, field service and CRM together on one platform, with a shared customer record. You turn it on module by module and import customers, contracts and inventory from Excel with visual mapping. Settings has import and export with templates: columns are recognized by name, and errors come out row by row, ready to download. It connects to your ERP in both directions, and the ERP still issues the invoice: attendo is not an ERP or accounting software. - [The attendo platform](https://attendo.me/en) - [Integrations](https://attendo.me/en/integrations) - [All modules](https://attendo.me/en/modules) ## More on choosing and rolling out software ### 40 questions to ask before you buy a CMMS Take this list to every demo. It works with any maintenance software vendor: buyers who ask good questions end up with the right software. And it is better to find out before you sign than three months later. 4 min read ### How to write an RFP for maintenance software A badly written RFP goes wrong in one of two ways. Either it leans toward one vendor and invites a protest, or it is so generic that the cheapest, weakest bid wins. This guide is about avoiding both. 4 min read Processes and compliance ### Which processes to automate first, and which to leave alone Automating the wrong process costs you twice: the time to build it and the time to undo it. Three simple questions separate what is worth automating now from what is better left alone. 4 min read [All blog articles](https://attendo.me/en/blog) ## Shall we look at it with your operation? Tell us how you work today and we will show you attendo with your own data. If it is not a fit, we will say so. - With your operation, not a generic demo - A real person from our team replies - No cold calls afterwards Would you rather talk first? - Phone [+34 910 053 530](tel:+34910053530) - Email [sales@attendo.me](mailto:sales@attendo.me) - Monday to Thursday 9:30 AM to 6:30 PM and Friday 9:30 AM to 2:30 PM (Spain time)