Business ERP in the cloud

How it is deployed

1. 1Inventory of the application, versions, integrations and licences.
2. 2Contact with the ERP vendor to confirm requirements and support on the new platform.
3. 3Environment build and test with real data during an agreed window.
4. 4Phased migration, performance validation and rollback plan.
5. 5Ongoing operation: monitoring, backups, updates and user support.

What Seintec operates, and what it does not

Seintec operates the server the ERP runs on, the operating system, the database engine, backups and their retention, the network, remote access publishing and resource monitoring. It also supports the workstations users connect from where end-user support is contracted. Functional development of the ERP, its configuration, custom reports and vendor licences fall outside that scope and remain with the software reseller. The boundary is written into the proposal, together with the escalation procedure between both parties, so an incident is never left waiting while ownership is debated.

What is at stake if it is left unaddressed

• Backups that have never been restored

  A backup nobody has ever restored is an assumption, not a safeguard. Periodic tests confirm the file is usable and how long a return to service actually takes.

• Improvised remote access

  Remote desktops published straight to the internet, or a VPN account shared between people, remain the most common way in. Access should be named and protected with multi-factor authentication.

• Reliance on one individual

  When only one technician or software reseller knows how the environment is built, every incident begins with an investigation. Documented inventory removes that bottleneck.

Frequently asked questions

Do we have to change ERP or software provider?

No. The usual approach is to keep the ERP and its maintainer: Seintec operates the infrastructure and coordinates windows, versions and requirements with them.

Can any ERP be hosted?

It depends on technical requirements and the vendor's licensing terms. We verify this before proposing anything; if it is not feasible, we say so.

What about printers and peripherals?

They are reviewed in the initial inventory. Printing, scanners, scales or digital signatures are tested during the pilot before moving all users.

How do we know it worked?

Through performance tests on real processes (reports, closings, order entry) compared with the previous environment and validated by key users.

How much downtime does the migration involve?

The migration runs in phases within an agreed window, usually outside production hours or over a weekend. The new environment is built in parallel and tested with real data first, so the cutover is limited to the final copy and the change of access. A rollback to the previous environment stays available until the new one is signed off.

Who handles a problem inside the application, Seintec or the ERP vendor?

Seintec is responsible for the infrastructure: server, operating system, database, backups, network and access. How the application behaves is maintained by its vendor or reseller. What matters is that the split is written down from the start and that someone coordinates both sides instead of leaving the company in the middle.

Does our data leave Spain?

No. The infrastructure is delivered from our own datacentre in Sant Miquel de Balenyà, in the Osona area, province of Barcelona. That matters for companies with data-handling requirements, or with public-sector clients who ask where the information physically resides.

What information do you need to scope the project?

The management software and its version, the number of concurrent users, the current database size, how remote users work today and what backups exist. With that, realistic sizing is possible. Where the information is not available, it is gathered during an initial review of the environment before anything is proposed.