Who leads the migration of applications and data?
The customer or its integrator plans and validates applications, data, configurations, and rollback. ipcore prepares and coordinates the destination physical infrastructure.
PHYSICAL INFRASTRUCTURE MIGRATION · MADRID
Server migration and data center relocation
Moving servers out of an office or switching colocation providers, from anywhere in Spain, requires preparing the destination before disconnecting the origin.
ipcore prepares and coordinates at MAD-NE the physical destination of the migration: rack, power, connectivity, access, goods-in, racking, cabling, and checks. The customer or its integrator leads the logical migration of applications, data, dependencies, change windows, rollback, and functional validation.
DestinationMAD-NE
OriginAll of Spain
Goods-in24×7×365
ScopePhysical
01 / Migración
What types of change MAD-NE can receive
- moving servers from an office or technical room;
- switching from one data center to another;
- changing colocation provider;
- relocating one or more racks;
- adding an additional presence in Madrid;
- hardware renewal with direct installation at MAD-NE;
- outsourcing the physical layer of an in-house data center.
Feasibility depends on racks, power, connectivity, logistics, windows, and responsibilities.
02 / Migración
What ipcore coordinates and what the customer keeps
| Area | ipcore at MAD-NE | Customer or integrator |
|---|---|---|
| Physical destination | Rack, power, A+B, access, and procedures | Validate that the configuration meets the architecture |
| Connectivity | Coordinate the agreed delivery method | Define destinations, addressing, routes, and dependencies |
| Logistics | Goods-in and access coordination | Packaging, transport, and insurance unless otherwise agreed |
| Installation | Racking, cabling, and physical connection | Logical configuration and credentials |
| Change | Physical checks and environment availability | Window, sequence, rollback, and functional validation |
| Subsequent operations | Remote hands and authorized work | Administration of systems, applications, and data |
This split lets each party work on the layer it knows and controls: ipcore on the physical destination and the customer or its integrator on the systems and services.
03 / Migración
1. Inventory and scope
Before setting a date, it helps to identify:
- number and form factor of equipment;
- rack units and dimensions;
- approximate power;
- power feeds and connectors;
- interfaces and optics;
- network destinations;
- dependencies between systems;
- authorized persons;
- tasks each party will perform;
- change date and window.
A sufficient inventory makes it possible to prepare the destination and begin planning.
04 / Migración
2. Preparing MAD-NE before the move
The destination must be ready before disconnecting the equipment:
- reserve rack and power;
- define A+B power;
- contract and deliver connectivity;
- verify addressing and routes;
- agree on access and goods-in;
- prepare patch cords, optics, and physical material;
- document authorizations and contacts;
- confirm the installation sequence.
When connectivity is critical, it should be tested as far as possible before the change window.
05 / Migración
3. Change plan and rollback
The customer or its integrator must document:
- shutdown and power-on order;
- dependencies between services;
- backups and recovery;
- required configurations;
- success criteria;
- the point beyond which the change does not continue;
- conditions for returning to the previous environment;
- who is responsible for each decision.
ipcore coordinates the points that affect goods-in, access, physical installation, and connectivity, while the systems owner leads the functional sequence of the change.
06 / Migración
4. Transport and goods-in
Hardware goods-in is available 24×7×365, subject to coordination and authorization.
Before shipping, the following must be agreed:
- courier and reference;
- arrival date or window;
- number of packages;
- responsible person;
- expected condition of the packaging;
- destination within the facility;
- the action ipcore must take upon receipt.
The scope of unpacking, inspection, and handling of transport incidents must appear in the project instructions.
07 / Migración
5. Racking, cabling, and handover
ipcore can perform:
- racking of switches, routers, and servers;
- connection to the A and B feeds;
- agreed physical cabling;
- connection of the delivered circuits;
- visual and power checks;
- reboots or other authorized work;
- handover to the customer or integrator for logical configuration.
Testing of applications, databases, users, and services belongs to the customer's functional plan.
08 / Migración
6. Subsequent operations
After the change, remote hands make it possible to handle physical work without traveling:
- reboots;
- checks;
- component replacement;
- cabling;
- RMA;
- receiving or shipping equipment.
09 / Migración
Frequently asked questions
Can connectivity be prepared before moving the servers?
Yes. It must be defined and coordinated in advance. Delivery and the possibility of testing depend on the provider, the circuit, and the project.
Can ipcore receive the equipment even if the customer is not in Madrid?
Yes. Goods-in and physical work are available 24×7×365, subject to coordination, authorization, and contractual terms.
How is continuity protected during the move?
By preparing the rack, power, and connectivity in advance, defining a change window, and documenting backups, sequence, acceptance criteria, and rollback.
Can I move from another colocation provider to MAD-NE?
Yes. This page covers precisely the change of data center or provider, with destination preparation and physical coordination at MAD-NE.
What information do you need to get started?
Inventory, racks, power, connectivity, origin, target date, responsible persons, and the scope expected from ipcore.
10 / Migración
Choosing the destination before moving the infrastructure
The move should not begin until the destination has been compared against verifiable criteria: power continuity, cooling, connectivity, access, physical on-site support, contractual terms, and the ability to migrate again.
Next step
Tell us what is moving, from where, and by when.
With that context we can review the physical preparation of MAD-NE, the required connections, and each party's responsibilities.