Skip to content

Häufig gestellte Fragen

How long does the implementation of datapine take?
An ERP implementation takes 3 to 18 months depending on complexity. Cloud solutions are often productive within 4–12 weeks, while classic mid-market ERPs need 6–12 months for requirements analysis, customising, data migration and training. More under ERP implementation.
How secure is datapine with regard to data protection?
For cloud ERPs, the central criteria are server location (ideally EU/Germany), a data processing agreement (DPA) and BSI C5 or ISO 27001 certifications. GDPR compliance should be explicitly documented by the vendor. Standardised interface protocols (REST API, OData, EDIFACT, ZUGFeRD) are a must today and should be supported out of the box.
How is datapine developed further?
Cloud ERPs typically receive monthly to quarterly releases automatically. On-premises ERPs have annual major releases with active patch maintenance. Release notes and the roadmap can be viewed at the vendor.
What happens to my data if I cancel datapine?
With cloud ERPs, a good vendor guarantees data export in an open format (CSV, JSON, SQL dump). The contract should explicitly regulate the data return obligation, deletion period and format. Standardised interface protocols (REST API, OData, EDIFACT, ZUGFeRD) are a must today and should be supported out of the box.
What support SLAs does datapine offer?
Standard support usually covers weekdays 8 a.m.–6 p.m. with a response time of around 4 hours. Premium/24x7 SLAs cost extra. With cloud vendors, availability SLAs (e.g. 99.9%) are important — check the contract!