Deploy & Relocate
Plan the move around every physical handoff.
Leviathan offers physical equipment relocation and logistics, from the released origin inventory through removal, packing, transport arrangements, receiving and destination installation. We define the assets, handling requirements and responsibility at each handoff before the move begins.
Discuss a ProjectGive the move a defined origin and destination
A relocation changes more than an address. The origin needs authority to release the equipment; the destination needs space, access and an installation plan. Between them, packaging, custody, timing and exceptions determine whether the receiving team can account for what arrives.
This service suits a data-center move, a colocation change, an equipment consolidation or a physical refresh. We scope the movement and installation work around identified assets and the actual site rules. Applications, data disposition and service restart need their own named owners within the wider project.
Connect removal, logistics and reinstallation
Origin and destination planning
Reconcile the asset list, physical positions, destination layout, access routes, work windows and approval contacts at both sites.
Release and removal preparation
Identify the equipment authorized for physical work, its required disconnections and the parties providing shutdown and specialist releases.
Packing and logistics
Plan the agreed packaging, handling, transport arrangement and custody transfers for the actual equipment and route.
Destination receiving
Reconcile arriving identifiers and visible condition, record exceptions and identify the party authorized to accept the delivery.
Reinstallation and cable changes
Mount the agreed equipment, complete the included IT cabling and labels, and update the records for the destination arrangement.
Make each release a recorded decision
Inventory and map
Link each asset to its origin, intended destination and customer owner; distinguish equipment moving, remaining or being retired.
Confirm the move package
Agree handling methods, packaging, transport resources, custody, insurance requirements and the site-specific work sequence.
Move through the handoffs
Carry out the released physical stages and record transfers, visible exceptions and decisions that affect the destination plan.
Reconcile and close
Match the received and installed equipment to the agreed inventory, record remaining work and hand over the updated physical package.
Provide both site briefs
Start with origin and destination addresses, the asset list, models, dimensions and weights, ownership, current rack positions and proposed destination positions. Include access and loading rules, receiving contacts, work windows and the person authorized to release equipment from each site.
Identify the application shutdown, backup, data-disposition, electrical and cooling owners. Tell us which packaging is available and any OEM transport or handling requirements. Insurance, vehicles, specialist equipment, personnel and any partners are confirmed for the engagement; they are not inferred from the existence of a move date.
Keep the asset story intact
The agreed record set can link the origin inventory to receiving and reinstallation without inventing a successful move in advance.
Move inventory and destination map
Equipment identifier, origin position, intended destination, ownership and the scope of any replacement or retirement.
Custody and condition record
Agreed transfer points, accepting parties and recorded condition or discrepancies, with photographs only where authorized.
Destination reconciliation
Received and installed identifiers, rack positions, included cable/label changes and items that did not reach the expected state.
Exception and closure list
Missing or damaged items, deferred work, decision owners and evidence needed for the customer to close the physical package.
Agree the parties and the returned scope
Two relocation proposals can name the same destination while leaving different work with the customer. Compare the actual stage ownership and returned records before treating their scope as equivalent.
Start with the physical stages you need and identify which are requested from Leviathan, which the customer has already placed with another party and which remain unconfirmed. A customer-appointed carrier or receiving team can be part of the project without becoming a Leviathan partner or an included resource. Confirm the actual arrangements and interfaces for the engagement.
For each included stage, agree the input it relies on, the party doing the work, the handoff point and the record returned. Name who can receive a package, who can resolve an exception and who reviews the physical installation output. These can be different roles. A receipt identifies a transfer or observation; its commercial meaning and any acceptance or liability terms belong in the actual agreements.
An origin that can release the agreed assets
Identify the customer asset owner, site release contact and separately appointed shutdown, data and specialist owners. State which release evidence the physical package will reference. An instruction to collect equipment is not itself proof that the surrounding systems have been released.
A confirmed logistics interface
Identify who arranges the agreed packaging, handling and transport, the actual transfer points and the contact who can decide when a dependency changes. If those services are customer-appointed, make that retained scope visible. Vehicles, storage, specialist equipment, insurance and personnel are confirmed separately for the engagement; no resource is assumed available from this page.
A destination with separate receipt and installation roles
Identify the receiving contact, permitted receiving or staging arrangement and the installation owner. State what the receiving record must return and which issued destination inputs the installation package relies on. If the receiving party cannot authorize installation, give that next decision to the actual responsible owner instead of leaving the arrival record to imply it.
A defined physical result and its reviewer
Agree which included installation, cabling/label and location records the customer will review, with an exception list for work not achieved. Identify separately the owners of technical verification, service transition and any later removal or disposition. Scope comparison should show both the included result and the customer-retained decisions.
Decide what a destination change does to the package
A receiving arrangement, installation release and service restart are different dependencies. Plan who will decide when one changes rather than assume the physical team can solve the gap on arrival.
Illustrative scope discussion: the customer has appointed the carrier and destination receiving team, while the proposed Leviathan package covers agreed destination installation. Before the move is released, the destination installation approval is reported as outstanding. The customer must establish the disposition with the relevant site and technical owners. The example supplies no carrier booking, available storage, approved alternate location or completed move.
If a permitted receiving or staging arrangement is confirmed, record its actual scope and the owner of the next installation decision. If it is not confirmed, do not describe delivery into staging as an available fallback. The agreed parties must determine what the changed dependency means for their own packages before a task relies on it; timing, commercial consequences and logistics changes are handled through the actual engagement arrangements.
Keep the changed input visible
Reference the affected destination instruction and its issue, what changed, who raised it and the receiving decision owner. Preserve the earlier instruction as history. A new date alone does not resolve a missing site release, changed destination or unavailable receiving arrangement.
Reconfirm the affected scope
Identify which removal, transport, receipt or installation package depends on the changed input and request its responsible owner’s disposition. Do not silently add storage, another destination, extra handling or an extended attendance commitment to the physical scope. Confirm any revised arrangements explicitly.
Close only the result actually evidenced
The returned physical package identifies completed included work, the issued records it used and remaining items with owners. Destination receipt or installation completion does not authorize application restart, technical acceptance or retirement of the source system. The customer and appointed technical owners provide those separate decisions.
Separate the physical move from the surrounding systems
Liquid-side connections and disconnections and facility electrical construction remain excluded. Customer/OEM and facility specialists must provide the required releases before affected physical work. Structural approvals, heavy-handling requirements and any licensed design authority need explicit project ownership.
Application migration, BIOS or firmware changes, IP/network configuration, OS imaging and software commissioning are not standard relocation inclusions. Bring additional requests into the scope discussion. The customer assigns data destruction, recycling, resale and other asset-disposition decisions to the appointed qualified providers under their own arrangements and evidence requirements; a physical removal record does not establish those outcomes.
Project questions
Does this include software commissioning?
BIOS, firmware, IP configuration, OS imaging and complete software commissioning are not standard services. The project scope identifies separate system responsibilities and any additional requirements before work begins.
Can a customer-appointed carrier or receiving team be part of the move?
Yes, the scope discussion can identify work retained with customer-appointed parties and the interfaces to the requested Leviathan package. Confirm the actual parties, transfer points, input records and decision contacts. Their participation does not establish a Leviathan partnership, a transport resource or an included service.
How should we compare two physical relocation scopes?
Compare the included stages and returned result, not only the origin, destination or date. Identify who releases equipment, supplies the agreed logistics, receives it, installs it, returns the records and resolves exceptions. Keep customer-retained and unconfirmed work visible; a lower or broader-looking scope description does not settle those interfaces.
Does delivery to the destination mean installation can proceed?
No. The receiving arrangement and installation release are separate. Any permitted staging, final location and required site or specialist decisions must be established for the actual package. This page does not promise available storage or an approved alternate destination.
What should the physical handoff say if some work remains open?
Identify the included result actually evidenced, the applicable record issues, incomplete work and its decision owner. Keep receipt, installation completion and customer technical or service-release decisions distinct. An exception list does not itself approve the unresolved work or change the engagement terms.
Discuss the origin, destination and move window
Send a nonconfidential asset summary, the two site locations and the intended physical move. Identify the open dependencies so we can discuss the work package, logistics and availability.
Discuss a ProjectEmail Project Scope