Moving from database to XML synchronizationsMoving from database to XML synchronizations

Introduction

Support for database synchronizations in Pure will be discontinued from June 2026, as announced in the 5.28.0 release notes. If you are currently using database views as the source for synchronizing data into your Pure, you will need to switch to a supported method: either XML synchronizations or the Pure write API. For the differences, see Pure API vs XML Synchronization.

This article focuses on the process of moving from database to XML synchronizations. A Pure & Simple webinar was also held on this topic on 29 April 2024; to watch the recording visit the Events page of the Pure Product Support Portal.

Preparation

When preparing to move from database to XML syncs, consider:

• What synchronization jobs are you using?
  • The Configurable Synchronizations, e.g. Configurable Person Synchronization - though note that the job name can be changed manually. These are the latest versions and cover most content types; the configurations allow you to 'Sync', 'Sync once', 'Do not sync' or 'Lock field' on most fields and you can choose ‘Database’, ‘XML’, ‘XML upload’ or ‘Excel’ as data sources. These jobs will work in exactly the same way when you switch the data source setting from database to XML.
  • Older synchronizations. These have more limited functionality. You should switch to the Configurable Synchronization jobs as part of your move to XML synchronizations. See Transitioning to the Configurable Synchronization.
• What will be the source of your XML files?
  • Your existing database views. This can save time and effort, but requires you to maintain the database.
  • The source system that feeds the database. This will give you more flexibility as well as the opportunity to merge data from more sources, but requires more time and effort. 
• Where will you store your XML files, and how will you grant Pure access to them? See Securing access to a synchronization source. 
  • On an HTTPS web server managed by you, secured with username/password or by IP.
  • In an Azure storage container managed by you, secured by IP and/or with SAS key.
  • In an Amazon S3 bucket managed by you, secured with VPN and token.
• Do you have a Pure staging server you can use to test XML synchronizations?
  • If not, please raise a case on the Pure Product Support Portal for assistance.
• Will you change the source IDs for records when you switch from database to XML?
  • If yes, refer to the job Bulk Change Source IDs on Content.

 Recommended process

1.  Copy your production server data to your staging server.
2. Map and generate XML files for each content type based on existing database views or other sources. See, e.g., Organization XML, User XML and Person XML.
   1. Automate data extraction from your source.
   2. Automate XML transformation to match the Pure data model.
   3. Validate XMLs against XSDs, or test by bulk importing (the latest XSDs and XML examples can be found in Pure at Administrator > Bulk import). See Bulk Import vs. Synchronization: A Definition.
   4. Ask Pure Support if you are having difficulties with the XML format.
3. Set up XML storage server.
   1. Automate transfer to XML storage.
4. Configure the Configurable Synchronization jobs to use XML instead of database (and disable any old synchronization jobs).
   1. Adjust settings such as safe size and notifications as needed.
   2. Adjust metadata field behaviour (sync, sync once etc.) as needed.
5. Run sync job.
   1. Check job log for errors and warnings.
   2. Ensure that all included data is updated and correct - if not, delete data and iterate, and/or restore Pure if needed.

Differences between database and XML synchronizations

Help

For assistance with specific problems, such as job configurations or XML structure, raise a case on the Pure Product Support Portal.

If you would like to be guided through the process by a Pure expert, contact your Customer Success Manager.