Created question in FIWARE Q/A platform on 12-04-2019 at 12:04
Please, ANSWER this question AT https://stackoverflow.com/questions/55649271/migrating-previously-collected-datasets-to-fiware-backend

Question:
Migrating previously collected datasets to FIWARE backend

Description:
Having at hand, the task of migrating previously collected environmental datasets (weather, airquality, noise etc) from sensors deployed in different locations, and stored in several tables of MySQL database, to my instance of fiware Orion CB, and thus persisted to fiware backend.

The challenges are many:

the data isn't stored in fiware standards, so must be transformed according to the fiware data models.
not all tables are a good candidates of being transformed to an Entity.
some Entities need have field values from several tables as attributes. For instance, defining AirQualityObserved Entity-type would have attributes from these tables: airquality, co, co2, no2 and deployment. So mapping these attributes to a particular Entity-type is a challenge.

As this is a one-time upload (not live data), I am thinking of two possibilities to go about it.

Add an LwM2M client, to keep sending data to an IoTAgent and eventually passed to Orion CB until the last record.
Create a Python script that "pretends" to be a contextProvider to the Orion instance, sending data (say every 5sec) until the last record.

I have not come across a case in my literature search that addresses such a situation. Is there any recommendations from FIWARE Foundation for situations similar to this?

How would you suggest about data fields --> Entity's attributes mapping that actually need be combined from several tables?