Config Import/Export for WordPress – Ingestics
Configuration Export
Ingestics configurations are fully portable. You can export your entire setup – providers, campaigns, settings, templates, filters, and taxonomy rules – as a single package file. This file can be imported on another WordPress installation running Ingestics, replicating your configuration without manual re-entry.
What Can Be Exported
| Component | Description | Exported |
|---|---|---|
| Providers | All API and RSS provider configurations | Yes |
| Campaigns | Campaign definitions and provider associations | Yes |
| Settings | Global plugin settings and preferences | Yes |
| Templates | Post templates and content layouts | Yes |
| Filters | Content filters and field mapping rules | Yes |
| Taxonomy rules | Category and tag assignment rules | Yes |
| Credentials | API keys and passwords | Redacted (masked with asterisks) |
Credential Redaction on Export
When you export a configuration package, all API keys, passwords, and other sensitive credentials are redacted. Each credential is replaced with asterisks in the export file. When the package is imported on another site, you will need to re-enter the credentials manually. This ensures that exporting and transferring configurations never exposes sensitive authentication data.
Import on Another Site
Importing a configuration package restores all components on the target site. Providers, campaigns, settings, templates, filters, and taxonomy rules are recreated exactly as they were on the source site. The import process skips any items that already exist on the target site to avoid duplicates, and it reports what was imported and what was skipped.
Use Cases
- Staging to production: Build and test your provider configurations on a staging site, then export and import them to production
- Site migration: Move your entire Ingestics setup when migrating to a new WordPress installation
- Agency deployment: Create a standard configuration once, then deploy it across multiple client sites
- Backup: Export your configuration as a backup that can be restored if needed
Tier Availability
| Tier | Config Portability |
|---|---|
| Free | Not available |
| Lite | Not available |
| Pro | Full export and import with credential redaction |
| Business | All portability features, multi-site deployment support |
Frequently Asked Questions
Are API keys included in the export file?
No. All credentials – API keys, passwords, tokens – are redacted in the export file and replaced with asterisks. You must re-enter credentials manually after importing the package on the target site.
Can I import a configuration package on a site that already has providers configured?
Yes. The import process detects existing items and skips them to avoid duplicates. It reports which items were imported and which were skipped, so you know exactly what changed.
Is the export file human-readable?
The export file is a structured data format. While it is not designed for manual editing, it can be inspected to verify what will be imported before running the import process.
Start automating.
Download Ingestics free. Start fetching APIs and RSS feeds in minutes.