Move dashboards, funnels, cohorts and other saved configuration between projects as one file. Export from one project, review the file, and import it into another.
What Config Transfer is
Config Transfer moves the things you built in one Countly project into another, without rebuilding them by hand. A dashboard, a funnel, a cohort, a saved Drill query: each is a configuration, and Config Transfer exports a set of them from one project as a single file, then imports that file into another.
It sits under Manage and is bound to the project in the scope bar. The Export tab reads configurations from that project and downloads the ones you pick. The Import tab takes a file and writes its configurations into that project. Moving setup between projects is therefore two visits: scope to the source and export, then scope to the destination and import.
Import changes a project, so it is offered only to members who may update that project's configuration. A member without that right sees the Export tab alone, and a link straight to the Import tab lands them on Export.
What happens when you import
An import is a reviewed action in two parts. First the file is read on your side and shown back to you as its contents: which features it holds, how many items of each, and the first of their names. Nothing has been written yet. Then you confirm in the bar at the bottom, and the summary that comes back says what happened to every feature in the file.
The summary sorts each feature into four outcomes. Imported counts the items written into the project. Skipped counts items the import left alone, with the reason beside each feature. Imported with warnings counts items that were written but carry a message about something in them that did not resolve in this project. Not imported counts items the project refused to write, with the reason beside each feature, such as an experiment whose adaptive variable is not in this project; the rest of the file is still applied. A skip is not a failure and neither is a warning; both are the import telling you what it decided.
Use Cases
Copy a project’s setup to another project
A new project should start with the dashboards, funnels, and cohorts the existing one already has.
- Open Manage > Config Transfer and, in the scope bar, pick the project you are copying from. The caption beside it confirms which project the export reads.
- On the Export tab, tick what you want in the Configurations panel: a whole feature, or expand it and tick individual items. Everything you tick appears in Selected for export on the right.
- Choose Export as file. One JSON file downloads, named after the project and the date.
- Switch the scope bar to the destination project and open the Import tab. The caption now names that project.
- Drop the file in, read the File contents card, and choose Import now.
Back up configurations before a big change
You are about to reorganize dashboards or rewrite cohorts, and you want a way back.
- On the Export tab, with the search box empty, tick the master checkbox in the picker toolbar. With no search active it selects every feature the project has.
- Choose Export as file and keep the file somewhere you will find it. Its name carries the project and the date, so several backups stay apart.
- Make your changes.
- If you need to go back, import the file into the same project and read the summary: what was written, what was skipped and why, and what was written with a warning.
Review a file before you import it
Someone sent you an export file, and you want to know what it will do before it touches the project.
- Check the scope bar first. The caption beside it names the project the file will be imported into, and that is the only project the import writes to.
- Drop the file on the Import tab. Its contents are read on your side and listed under File contents: each feature with its item count and the first eight names in it.
- A file that is not a configuration export, or is far too large to be one, is refused at that point. The tab says why, and the Import now bar never appears.
- When the contents are what you expect, choose Import now in the bar at the bottom, which repeats the item count and the project name. Choose Discard to drop the file instead.
FAQs
Why do I not see the Import tab?
You do not have the right to update this project's configuration. Export is available to anyone who can read the project; Import needs the update right, and the tab is hidden rather than shown disabled.
Why is a feature missing from the Configurations panel?
Either the project has nothing of that kind to export, or you are not allowed to read it. In both cases the panel has nothing to show for that feature, so it leaves it out.
Does importing overwrite what is already in the project?
Read the summary that comes back. Items the import left alone are listed under Skipped, with the reason beside each feature. Items that were written but reference something this project does not have are under Imported with warnings. Items the project refused to write are under Not imported, with the reason.
Can I import into the same project I exported from?
Yes. The Import tab takes a file exported from this or another Countly project, and it writes into whichever project the scope bar names.
Is any data in the file?
No. The file holds configuration only: dashboards, funnels, cohorts, saved queries, and the other features listed under What can be transferred. Sessions, events, profiles, and crashes never leave the project this way.