Importing / Exporting Custom Cards
Purpose and Intended use
The import/export capability lets you export a custom card as an .en8Card file and import it back in. It was introduced to support a specific maintenance scenario, not as a general-purpose way of moving custom cards between different environments or systems. Please read the limitation below before using it.
This capability was originally built to help customers update existing custom cards following an update to the underlying UI rendering library. When that library changed, custom cards built beforehand needed to be adjusted to remain compatible, and this import/export flow was the supported way to make and reapply those changes.
The intended workflow is:
Take a backup of your production database.
Restore that backup into a sandbox / integration database.
Make the required changes to the custom card in that environment so it is compatible with the updated rendering.
Export the updated custom card from the sandbox as an
.en8Cardfile.Import the card back into your production system.
Because step 2 restores an exact copy of production, the source and target databases are identical at the point of export and import — which is the condition this capability depends on (see below).
Important:
This capability only works when the source and target systems are exact copies of the same database (for example, a production backup restored into a sandbox, as described above).
It cannot be used to move a custom card between two different / independently built systems.
Why: when a card is imported, its data fields are matched using their underlying unique identifier (GUID), not the field name. If the two systems are not copies of one another, the GUIDs will not match — even when the field names appear identical — so the import will not resolve the fields correctly.
In short:
✅ Supported — moving a card between environments that are copies of the same database (e.g. a backup restored into a sandbox, then back to production).
❌ Not supported — moving a card between two different systems that were built independently, as the field GUIDs will differ.
Exporting Custom Cards
To export a card, select the desired card(s) from the main screen list and select the export link

These will automatically export to your downloads folder. as '.en8Card ' files.
Importing Custom Cards
To import a card, select the import link and in the resulting screens select the '.en8Card ' files you wish to import

If the card is a duplicate (shares same Card name) as an existing form you will be asked to confirm updating of that card..

Last updated
Was this helpful?