Using OSF FieldStorage to Synchronize Existing Drupal Local Content to OSF

If the  is installed and enabled on a non-vanilla Drupal 7 instance (a Drupal 7 instance where content type data has already been created), it means that the Drupal site developer probably want to migrate all the content types content that is currently indexed into the default field storage system (namely, MySQL) before switching the content type (node) field storage system from the default one which is "field_sql_storage" (MySQL) to the   one (OSF). Here are the steps to migrate that information, and then to configure the  module to start using OSF as the default field storage system for all the selected content types:
 * 1) Before configuring the   module, you have to migrate all the content type data you want to migrate to OSF before proceeding with switching the field storage system.
 * 2) The data migration is done using the Search API Indexer
 * 3) Read this documentation to know how you have to create an indexer to migrate all the information. What you have to do here is to map all the fields you want to migrate to the appropriate Ontology property. Then you have to select the dataset where you want to index the local content. Once this is done, following these steps, you have to run the indexer to migrate all the local content into OSF.
 * 4) Once the local content is fully mapped and migrated, you can proceed with the following steps
 * 5) The default field storage system should be configured such that it is   that is used by default instead of  . This means that for all the future fields that will be created within the content types, the storage system that will be used will be   instead of.
 * 6) Go here
 * 7) Check the   checkbox
 * 8) Click the   button
 * 9) Select a OSF dataset where the Drupal Content Type nodes will be indexed
 * 10) Go here
 * 11) Select the dataset where to save the Content Types data
 * 12) Note: this has to be the same dataset that has been used in the local content migration step #1 above
 * 13) Click the   button
 * 14) Once the   module is properly configured, the next step is to properly configure the different content types you want to use
 * 15) Go here
 * 16) Click   for the Content Type(s) you want to configure
 * 17) You will notice a new column called  . All new fields should display   as the storage type being used. For all existing fields, you should see.
 * 18) If you want one of the fields that is currently using the   field storage system to use the   then you have to:
 * 19) Delete the current field
 * 20) Recreate it using the normal Drupal field creation procedure
 * 21) Note 1: you should be doing this for all the fields you migrated using the migration procedure in step #1
 * 22) Note 2: by deleting the field, you will be deleting the data associated to that field in the previous field storage system (probably MySQL)
 * 23) Note 3: the revisions of the content type nodes are not migrated
 * 24) Once all the required fields uses the   field storage system, then the next step is to map all these fields to the appropriate RDF classes and properties
 * 25) Go here   (or click the   content type tab)
 * 26) Make sure that you are linking the type to an Ontology class, and make sure to map all the fields to a Ontology property.
 * 27) Note: it is crucial that the mapping is exactly the same one as the one used in the migration step #1 above
 * 28) Finally click
 * 29) You are now done. As soon as you will create a new content type node, all the fields that are using the   field storage system will be saved into OSF as specified into the setting above