Skyvia replication operation is used to create a copy of cloud application data in a relational database and keep it up-to-date. When performing replication, you define application objects and their fields to copy and configure replication options. Unlike Import, replication does not support loading data of different structure in source and in target and using any custom mapping, however it is much simpler to configure.
Replication can be used when you need to backup cloud application data to a relational database, archiving or historical data that is no more a subject to change and is not needed in the cloud application. It can be useful in different data integration scenarios, or just for performing data analysis and reporting with powerful data analysis and reporting tools, developed for relational databases.
Skyvia can create corresponding database tables automatically with optional foreign keys, and, if necessary, drop existing tables before creating. If you need to keep the copy in the database up-to-date, you can schedule package for automatic execution and use the Incremental Updates feature, which allows copying only the data that was changed in the cloud CRM since the last package execution, and then applying only the necessary changes to the database. In case the Incremental Updates check box is selected, table creation and dropping is performed only for the first package run if the corresponding check boxes are selected. Note that in some sources Incremental updates are not supported for some of the objects. See details for each source in the Connections section.
Skyvia allows you to filter data to replicate.
For more information see the replication tutorial - Setting Up Replication of Salesforce Accounts and Contacts to SQL Azure.
Skyvia doesn't create foreign keys, corresponding to many-to-many CRM object relations, in the database.