Introduction

The Export/Import feature allows you to backup your GDPR compliance configuration and transfer settings between websites. This is invaluable for agencies managing multiple client sites, developers working across staging and production environments, or anyone who wants to ensure their carefully configured settings are backed up.

With a single click, you can export all your plugin settings to a JSON file and import them on another site, saving hours of manual reconfiguration.

Why Use Export/Import?

Common Use Cases

1. Multi-Site Management

  • Configure once, deploy to multiple client sites
  • Maintain consistent GDPR compliance across portfolio
  • Standardize cookie consent implementation
  • Save time on repeated configuration

2. Staging to Production

  • Perfect settings on staging environment
  • Test thoroughly before going live
  • Export from staging, import to production
  • Ensure identical configuration

3. Backup and Recovery

  • Create backup before making major changes
  • Restore settings if something goes wrong
  • Keep historical configuration snapshots
  • Document configuration changes over time

4. Site Migration

  • Moving to new hosting provider
  • WordPress migration tools
  • Domain changes
  • Preserve GDPR settings during migration

5. Template for New Sites

  • Create “gold standard” configuration
  • Use as starting point for new projects
  • Ensure all sites meet minimum compliance
  • Reduce setup time for new clients

Exporting Settings

How to Export

  1. Log in to WordPress admin dashboard
  2. Go to Settings → PureDevs GDPR compliance
  3. Click the Export/Import tab
  4. In the Export section, click Export Settings button
  5. A JSON file will download to your computer
  6. Save the file in a secure location

What Gets Exported

The export file includes all plugin settings:

  • General Settings: Enable/disable, banner position, cookie expiration
  • Banner Settings: Message text, colors, styling
  • Button Settings: Button labels, colors, positioning
  • Privacy Overview: Privacy policy links, terms links
  • Cookie Categories: All category configurations and descriptions
  • Geo-Location: Country targeting settings
  • Floating Button: Button appearance and positioning

Export File Format

The exported file is in JSON format:

  • Filename: puredevs-gdpr-settings-YYYY-MM-DD.json
  • Format: Human-readable JSON
  • Size: Typically 5-20KB
  • Encoding: UTF-8
Pro Tip

Name your export files descriptively, like “client-name-gdpr-production-2025-01-15.json” to easily identify what each backup contains.

Importing Settings

How to Import

  1. Go to Settings → PureDevs GDPR compliance
  2. Click the Export/Import tab
  3. In the Import section, click Choose File
  4. Select the JSON file you exported earlier
  5. Click Import Settings button
  6. Wait for confirmation message
  7. Review imported settings on other tabs

Import Behavior

When you import settings:

  • Overwrites: All existing settings are replaced
  • Complete Replacement: Current configuration is lost (unless backed up)
  • Immediate Effect: Changes take effect right away
  • No Merge: Doesn’t merge with existing settings, completely replaces
Important

Before importing, export your current settings first as a backup. Import will overwrite ALL existing configuration.

Export/Import Best Practices

Backup Strategy

  • Regular Backups: Export settings monthly or after major changes
  • Version Control: Keep dated versions of exports
  • Secure Storage: Store exports in secure, backed-up location
  • Documentation: Note what changed in each version
  • Pre-Change Backup: Always export before making big changes

Multi-Site Management

  • Master Configuration: Create one perfect setup
  • Site-Specific Adjustments: Import, then customize as needed
  • Update Strategy: When updating master, re-deploy to all sites
  • Testing First: Test on staging before deploying to all production sites

Safety Practices

  • Export Before Import: Always backup current settings first
  • Review After Import: Check all tabs to verify settings
  • Test Functionality: Test banner appearance after import
  • Verify URLs: Privacy policy URLs may need updating
  • Check Geo-Targeting: Ensure appropriate for target site

File Management

  • Descriptive Names: Include site name and date
  • Organized Storage: Keep exports in dedicated folder
  • Cloud Backup: Store in cloud for disaster recovery
  • Access Control: Secure folder with sensitive configurations

Transferring Specific Settings

Manual Selective Transfer

While plugin doesn’t support partial imports, you can manually transfer specific settings:

  1. Export settings from source site
  2. Open JSON file in text editor
  3. Copy specific section (e.g., banner_settings)
  4. Export settings from destination site
  5. Open destination JSON in text editor
  6. Paste copied section, replacing existing
  7. Import modified JSON to destination site
Advanced Users Only

Manual JSON editing requires technical knowledge. Invalid JSON syntax will cause import to fail. Always keep backup before attempting manual edits.

Troubleshooting Export/Import

Export button doesn’t work

  • Check browser doesn’t block downloads
  • Try different browser
  • Check PHP memory limit
  • Look for JavaScript errors in console

Import fails with error

  • Verify JSON file isn’t corrupted
  • Ensure file is from same plugin (not different GDPR plugin)
  • Check file size isn’t too large
  • Verify upload_max_filesize PHP setting
  • Try re-exporting and importing again

“Invalid file format” error

  • File must be JSON format
  • Don’t edit file unless you know JSON syntax
  • File may be corrupted during transfer
  • Re-download original export

Settings imported but don’t work

  • Clear site cache
  • Clear browser cache
  • Check privacy policy URLs are valid for new site
  • Verify geo-location settings are appropriate
  • Re-save settings manually on each tab

Import successful but some settings missing

  • Export may be from older plugin version
  • Some settings may not be compatible
  • Manually configure missing settings
  • Update plugin on both sites to same version

Version Compatibility

Plugin Version Differences

  • Same Version: 100% compatibility guaranteed
  • Minor Updates: Usually compatible (1.0.1 to 1.0.2)
  • Major Updates: May have new settings or changes (1.0 to 2.0)
  • Best Practice: Update both sites to same plugin version before import

Backward Compatibility

  • Newer plugin versions usually accept older exports
  • May add default values for new settings
  • Review all tabs after importing from older version

Forward Compatibility

  • Importing newer export into older plugin may fail
  • Older plugin won’t understand new settings
  • Update plugin before importing newer exports

Automation and Advanced Usage

WP-CLI Integration

For advanced users with WP-CLI access:

# Export settings
wp puredevs-gdpr export settings.json

# Import settings
wp puredevs-gdpr import settings.json

Note: Check plugin documentation for specific WP-CLI command availability

Deployment Scripts

  • Include export file in deployment repository
  • Automatically import during site setup
  • Part of automated WordPress installation
  • Ensures consistent configuration across environments

Version Control

  • Commit export files to Git repository
  • Track configuration changes over time
  • Document why settings changed in commit messages
  • Roll back to previous configuration if needed

Security Considerations

What’s in the Export File

  • Settings Only: No user data or consent logs
  • Configuration: Banner text, colors, URLs
  • No Secrets: No API keys or passwords
  • Public Info: Mostly public-facing content

Security Best Practices

  • Secure Storage: Store exports in protected location
  • Access Control: Limit who can import settings
  • Source Verification: Only import from trusted sources
  • File Integrity: Verify file hasn’t been tampered with
Privacy Note

Export files contain configuration settings only. They do NOT include user consent logs, IP addresses, or any personal data. They’re safe to share between your own sites.