Service Migrations
Moving data from one service to another with the help of automation
- Free consultation to determine your needs
- Free written execution plan without commitment
- Limited support after completion of project
Overview of the process
Whether your data comes from an Excel file, Website, API, or Database we have your back and can orchestrate transfer of your data from one service to another. A software application can be built in many layers and choosing from which layer to extract your company's data has implications on the kind of skills required to interact with that layer. The Reports layer tends to be the most accessible to non-technical users, but reports may be missing critical information useful for a service migration or custom programs may be necessary to stitch data elements together in a way that meets the new service's specifications. The database would be the ideal place for data extraction since its the primary source of your company's data, but the likelihood a software vendor provides access to that layer is unlikely. The solutions to extracting data in each layer will vary in time and complexity, but we can guide you through this process and tailor a unique solution based on your needs.
Extracting from BackendUsually faster and cheaperLess availableContact Us
Solution will involve connecting to a database and writing SQL statements to produce a CSV file. If CSV file is still not in correct format, custom scripts will be developed to complete anything more.
Databases are usually the preferred source for any sort of data extraction and transformation since it usually stores the original copy of your company data. Databases have structure, integrity, and a common language for communication called Structured Query Language (SQL) well known by most developers which makes data extraction a breeze. That paired with software tools which improve developer efficiency with SQL means it is normally the fastest and cheapest solution for most projects.
The problem with databases is larger software services are less willing to provide a direct database connection because:
- They cannot risk you stumbling across data that isn’t yours
- They do not want to reveal ‘trade secrets’ developed when storing your data
- Or they do not want to provide an easy way for you to move to a competing service
Extracting from MiddlewareGreat for integrationsFeatures are unpredictableContact Us
Solution will involve writing custom scripts to communicate with an API using authentication keys provided by client and producing the required data file all in one.
Application Programming Interfaces (APIs) are the second most common source for extracting data since this is the layer that larger software services intend for you to interact with to get data from the database in a secure way. API’s use the HTTP protocol which is the same protocol that websites use, but API’s are designed with automation scripts in mind and only provide raw data instead of visual components.
The most common problems APIs tend to face are availability and documentation.
- Creating an API layer to a software service requires time and resources to develop which small companies may forego until they have a larger customer-base.
- Even if an API was developed, it is also possible that some features on the website are not paralleled in the API layer – or that the API layer is incomplete and more features may appear in a later version.
- APIs also depend on software services providing documentation to developers on how to use it. This documentation and ease-of-use varies by service and can have consequences in data extraction.
Extracting from Front EndFirst thing to tryReports can be incompleteContact Us
Solution will involve writing custom scripts against reports generated by service and producing required data file all in one.
Websites are the most common source for extracting data by either downloading reports or writing programs to scrape the data automatically. The reason for this is the website is usually the first customer-facing tool developed by a software service provider and first place that new features appear to improve the service.
The most common problems with websites tend to be the lack of reports that are useful for service migration and the continuous change of available features.
- Reports are usually constructed in the context of the software service to provide summaries, not raw data elements. This means some data is completely missing or burdensome to stitch together.
- Websites changing means any automated tools used to interact with a website also need to be extra flexible to support changes in the underlying website layout. These changes can also be impossible to predict, usually warranting changes in the automated tool to fit the new layout.