®Data, security and migration
Migrating data from another business software.
Your data is not a technical detail. It is the company's memory.
Before go-live we define where the data is held, who can access it, how it is protected and which information to bring over from your current system.
The starting point
Answers about your data.
We do not promise "security" in the abstract. We document the infrastructure choices, access, backups and recovery activities that apply to your installation.
- EUThe cloud platform data is hosted in European data centres.
- 1 : 1Each user has their own credentials and permissions that match their role.
- 0No unverified re-entry: the migration ends with a check of the totals.
Data governance
Know where it is. Know who opens it.
The activation document describes the agreed configuration and the support channels. Requests for access, export or recovery follow a defined process.
- 01
Location: European data centres
The cloud platform uses infrastructure with data hosted in the European Union. Features and responsibilities are set out in the proposal and in the contracts.
- 02
Access: people, not shared accounts
Named credentials; roles and authorisations separate functions and managed companies. Where needed, access and sensitive operations are logged.
- 03
Protection: copies that can be restored
Backup strategy, frequency and recovery objectives are defined according to the service, with procedures and results you can read.
- 04
Portability: the data stays yours
XML for tax documents and tabular exports in the agreed formats, without depending on a screen.
The migration, step by step
How the migration is tested.
There is no reliable date until we have seen the archives. The plan is based on the quality of the data, the amount of history and the processes that must keep running during the changeover.
We read what exists
Customer and supplier records, items, price lists, stock levels, balances, open documents and history. We identify duplicates, gaps and available formats.
We choose what to bring over
Scope, start period and the data that will remain available for consultation in the previous system.
We test the conversion
The data goes into a test environment: mappings, balances, batches and stock value are checked before proceeding.
We prepare your people
Training uses real processes and documents. Each role knows what changes.
We go live
An agreed date, final checks and a support channel. The old system remains available for consultation for the agreed period.
Frequently asked questions
Before you start.
Can we keep all the history?
Together we assess which data to migrate and which to keep available for consultation in the current system. The choice depends on the format, the quality of the archives and how useful the history is for operations.
Does the company stop during the changeover?
The start-up plan takes into account the processes that must keep running. Any alignment windows and verification activities are agreed before the go-live date.
Who can see another company's data?
Multi-company installations separate data by organisation. A user can only access the companies and functions they are authorised for.
How do we ask for a copy of our data?
Through the eNerds contact details. The request is linked to the correct company and installation; format, scope and delivery are agreed and recorded.
Which archives are you starting from?
Tell us what you use today and which archives you want to bring across. We assess the route without generic promises.