# Best practices for Migrating CData Sync from a previous .NET version to V24 Cross-Platform in an IIS Deployment **URL:** \ **Category:** Editions\ **Tags:** article, cdata-sync, iis\ **Created:** [July 1, 2024, 5:35pm UTC](https://community.cdata.com/t/best-practices-for-migrating-cdata-sync-from-a-previous-net-version-to-v24-cross-platform-in-an-iis-deployment/809 "2024-07-01T17:35:23Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Bukuroshe\_D](https://avatars.discourse-cdn.com/v4/letter/b/50afbb/32.png) [@Bukuroshe\_D](https://community.cdata.com/u/Bukuroshe_D)\ **Post date:** [July 1, 2024, 5:35pm UTC](https://community.cdata.com/t/best-practices-for-migrating-cdata-sync-from-a-previous-net-version-to-v24-cross-platform-in-an-iis-deployment/809/1 "2024-07-01T17:35:24Z")
Starting with Sync 2024, the .NET edition of the application is deprecated. A general guide about _“Migrating CData Sync from the .NET Edition to the Cross-Platform Edition”_ can be found on the following article: [_Migrating CData Sync from the .NET Edition to the Cross-Platform Edition | Community_](https://community.cdata.com/how-to-with-cdata-72/migrating-cdata-sync-from-the-net-edition-to-the-cross-platform-edition-818?tid=818&fid=72) . Among the users that need to migrate their current .NET edition of Sync to the Cross-Platform edition are the ones using the .NET version of Sync deployed on the Microsoft IIS web server. This article provides general recommendations and detailed steps for performing this migration seamlessly, ensuring minimal disruption and maintaining the integrity of your data. **I. Recommendations:** **1. Setup a Development or Trial instance** Before proceeding with the migration on your production server, consider using a separate instance _(either a development or trial instance):_ - _If you already have a license that includes a key for development, you can use that instance to install the newer version of Sync._ - _Otherwise, to set up a trial instance, you can download Sync_ _from the_ [_CData website_](https://www.cdata.com/sync/builds/)_._ This will allow you to test the migration process and ensure all configurations work as expected. **2. Deploy Sync on IIS after verifying that everything works correctly** Initially, you can avoid involving IIS. Simply install Sync 2024 version, export your settings from the previous version and then import them to V24. After ensuring that everything was imported successfully and works correctly, you can start the process of deploying CData Sync to Microsoft Internet Information Services (IIS). **3. Backup your existing setup** Backup your existing setup by renaming the application directory and installation folders. This way, if you encounter any issues with the new installation, you can revert by renaming the files back. **II. Step-by-step guide:** 1. If you are using the default SQLite application database, you _must **export your settings** _ because the Cross-Platform edition of Sync uses the Apache Derby database by default. You can export your settings by using the _ **Migration** _ tab on the [_Settings_](https://cdn.cdata.com/help/ASK/sync/Settings-Page.html) page in Sync: ![8b99782a-ebd1-41af-a772-8c1e9f60da15.png](https://us1.discourse-cdn.com/cdata/original/2X/9/97b0947552212da331cfc530bb661a43a0d7dd22.png) **2. Rename** the .NET application directory and installation folder so that the new Cross-Platform edition will be installed in a separate folder _(the default paths are “C:\ProgramData\ __**CData**__ ” and “C:\Program Files\CData\ __**CData Sync**__ ”)._ Before renaming the folders above, you must first stop the Sync application so that the files are not in use. Since the application is hosted on IIS, to stop the application you can [_stop the site_](https://prnt.sc/pwX6dbTpqcsN) where the application is configured or its dedicated [_application pool_](https://prnt.sc/ZS553rPsM3Pm). **3**. Download and install the Cross-Platform edition of Sync from the [_CData website_](https://www.cdata.com/sync/builds/). During the installation of Sync, in one of the windows you will be prompted to choose the components to install. You can [_uncheck_](https://prnt.sc/jrmho4h33SKB) the CData Sync Service since you will deploy Sync on IIS. **4**. Run Sync manually To start CData Sync without creating a service, use the Command Prompt (CMD) to open the sync.jar file in the installation directory, as shown [here](https://prnt.sc/r9X1YUugYOc8): _java -jar sync.jar_ **5.** In your browser, navigate to _[http://localhost](http://localhost):YourPortNumber/_ to access Sync: ![21cdc87b-9a2e-4967-bbb9-e1cdc5a5d31c.jpg](https://us1.discourse-cdn.com/cdata/original/1X/f5d4368e18403fd4c013b2269798237faab00168.jpeg) Once done, you can register on our license portal to manage and upgrade your license, as V24 will require a new license key: [_https://portal.cdata.com/_](https://portal.cdata.com/) _ **Note** __: The default port number is_ _ **8181**__._ **6. Import the settings** that you exported in step 1: ![9f3f1bd3-fa8c-4622-a803-ed123fedc249.png](https://us1.discourse-cdn.com/cdata/original/2X/c/c55237d114d1e1d3f9503dcd5971cbd2e0ed2692.png) _Please note that if in your previous .NET installation of Sync, you’ve had scheduling enabled in any of your jobs, you will have to re-enable it after migrating to the Cross-Platform edition. That’s because scheduling configuration will be_ [_saved but not enabled_](https://prnt.sc/by1bJ1FqcNL0)_._ **7**. After making sure that everything is intact and works correctly, _close the **command prompt** _ that you used to start Sync and start the process of deploying CData Sync to Microsoft Internet Information Services (IIS) by referring to the next steps. **8**. Deploy CData Sync to Microsoft Internet Information Services (IIS) following the steps as per the documentation here: [_CData Sync - Configuring the Server_](https://cdn.cdata.com/help/ASK/sync/Configuring-the-Server.html#deploying-cdata-sync-to-microsoft-internet-information-services-iis) **9**. In your browser, navigate to _[http://127.0.0.1](http://127.0.0.1):YourPortNumber_ to access Sync: ![b91305b2-bea6-49d3-a622-de228765c770.jpg](https://us1.discourse-cdn.com/cdata/original/2X/7/743c1dfb9dc47bddd12434377bcff7c5cc9f49eb.jpeg) And that’s it. You should be good to go. _Note__: In this article we first ran Sync manually_ _(without creating a service__) to make sure that everything works correctly on v24 before proceeding with deploying Sync on IIS. However, you can absolutely skip this step and start directly with deploying Sync on IIS and then import the settings._ Please reach out to [support@cdata.com](mailto:support@cdata.com) if you run into any issues.