Bulk import and export for packages
Use the Import bulk data page (at the center level, Configuration > Business details > Business setup > Import bulk data) to move package data in and out of Zenoti in bulk. The page lists the data objects you can work with by group and, for each object, the operations available to you. For packages the relevant groups are:
- Packages β package definitions and their associations, one object per data set: Series Package, Day Package, Package Service, Package Product, Package Bundled Product, Package Service Discount, Package Center (the center assignment list with center-specific pricing and tax groups), Bulk Package Expiry Update, and Bulk Package Expiry Update (Center Level).
- Balances βΊ Package Balances β the current remaining balance on guest-held packages.
Each object offers an export and, for most objects, a validated import β so package definitions, center associations, and balances can all be loaded from a file as well as exported.
Audience: Administrators who perform bulk package operations β data migration, periodic backups, audit preparation, or center-rollout planning.
On this page
- Before you begin
- The package objects at a glance
- Run a bulk operation
- Update and rename existing packages
- Import package balance data
- File format and template
- Worked example
- Tips
- Troubleshooting
- Related articles
Before you begin
Permission: Each object on the Import bulk data page is gated by its own check box under DataIO in the Administrator section of the security role, named after the object β for example SeriesPackageImport for series packages, DayPackageImport for day packages, PackageCenterImport for center associations, and CustomPackageImport for Package Balances. One check box covers both the import and the export of that object; an object you are not permitted to use does not appear in the list.
- Bulk import and export must be enabled for your organization; if the Import bulk data row is not shown under Business setup, contact Zenoti Support.
- Prepare the source file in the correct format before importing (see File format and template).
- For destructive or large operations, export a current snapshot first as your recovery baseline. There is no rollback mechanism β if an import changes data incorrectly, the recovery path is a corrective import based on your pre-import export.
The package objects at a glance
Every operation starts from the same three drop-downs (object group, object, operation) and differs only by the selection you make. Use this table as your reference:
| Group βΊ Object | Operations | Scope | Typical use |
|---|---|---|---|
| Packages βΊ Series Package, Day Package | Export, validated import | Package definitions (catalog attributes per package) | Audit, migration to another environment, bulk creation or update of the catalog including renaming packages. |
| Packages βΊ Package Service, Package Product, Package Bundled Product, Package Service Discount | Export, validated import | The service, product and bundled-product benefits attached to packages, and service-level discounts | Bulk benefit changes across many packages. |
| Packages βΊ Package Center | Export, validated import | Which packages are active in which centers, with per-center pricing and tax-group values | Planning a new-center rollout, auditing pricing consistency, migration reference. |
| Packages βΊ Bulk Package Expiry Update | Export, validated import | Expiry dates of sold guest packages | Extending or correcting expiry dates in bulk. |
| Packages βΊ Bulk Package Expiry Update (Center Level) | Export only | Expiry dates of sold guest packages, scoped to a center | Exporting an expiry snapshot for a specific center before making corrections via Bulk Package Expiry Update. |
| Balances βΊ Package Balances | Export, validated import | Current remaining balance for every guest-held package | Operational snapshot, reconciliation before a data change, correcting balance errors after a migration. |
Note: The objects you see depend on your organization's import configuration and on your permissions. The list above reflects the standard configuration.
Important: No import deactivates or deletes a package. No import object changes a package's active state, and none deletes a package definition. The objects above change package definitions, benefits, center assignments, expiry dates, and balances only. To activate or deactivate many packages at once, use the bulk action on the packages list instead β see Manage the packages list.
Run a bulk operation
- At the center level, navigate to Configuration > Business details > Business setup > Import bulk data.
- In the first drop-down, select the object group β Packages or Balances.
- In the second drop-down, select the object β for example Series Package or Package Balances.
- In the third drop-down, choose the operation:
- Export β click Continue. Zenoti confirms that the export is getting ready and emails you when it is done; the file also appears in the request list on the same page, where you can download it.
- Validate β upload your file to check it against the import rules without importing anything. Use this first on any new file.
- Validate and Import only valid rows β upload your file; rows that pass validation are imported and the rest are reported. Some objects also offer Validate and Import only if all rows are valid, which imports nothing unless the whole file passes.
- For an import, upload the prepared .csv or .xlsx file, click Continue, and monitor the request in the list on the same page. When it completes, review the validation and processing logs, then verify the data by spot-checking an affected package or, for balances, an affected guest's package in their profile β or by running the Packages report.
Update and rename existing packages
When you import a Series Package or Day Package file, Zenoti uses the Package Code column as the matching key:
- If the Package Code in a row matches an existing package in the organization, Zenoti updates that package's attributes β including its Name β rather than creating a new record.
- If the Package Code does not match any existing package, Zenoti creates a new package.
This means bulk renaming of existing packages is performed by supplying the unchanged Package Code alongside the desired new Name in the import file. You do not need to delete and recreate the package to rename it.
Important: Package names must be unique across the organization. Before importing renames, export the current catalog and review existing names to identify any conflicts. The precise behavior when a name conflict occurs is not enforced by a specific import-time rule for packages β Zenoti may update, skip, or flag the conflicting row. To avoid uncertainty, resolve all naming conflicts in the file before submitting.
To rename packages in bulk:
- Export the Series Package or Day Package object to obtain the current catalog with all package codes.
- In the exported file, update the Name column for the packages you want to rename. Leave the Package Code column unchanged.
- Import the file using Validate first to surface any name-conflict errors.
- Once validation passes, import using Validate and Import only valid rows or Validate and Import only if all rows are valid.
Import package balance data
Package balance data records the current remaining benefit balance on a guest-held package. The recommended workflow is:
- Export first β select Balances > Package Balances and choose Export to obtain the current state. This file is your recovery baseline.
- Edit the exported file β update the balance values in the file. Work only from the exported file to ensure all required columns and identifiers are present.
- Validate before importing β upload the edited file with the Validate operation to identify errors without affecting any live data.
- Import β once validation passes, import the file using the appropriate import operation.
Note: Balance imports are used primarily to correct balance errors after a migration or to bring in balances from an external system. The import floor is the sale date of the package β a balance associated with a date earlier than the package's sale date is rejected.
File format and template
- Imports accept .csv and .xlsx files. The expected columns for each object are defined by the template for that object β use the Download Templates link on the Import bulk data page rather than authoring a file from scratch.
- Invalid rows are reported in the validation log; with Validate and Import only valid rows the remaining valid rows still load. Test with a small batch (5β10 rows) before a large run to confirm the behavior matches your expectation.
- Exports are queued and delivered through the request list on the page (Zenoti emails you when the export is ready), not as an immediate browser download.
Worked example
Scenario: Your organization is retiring the name "Summer Glow Series" and replacing it with "Radiance Series" across 3 packages that share the same base template. Their package codes are PKG-1042, PKG-1043, and PKG-1044.
- Export the Series Package object to get the current file. Locate the three rows where Package Code = PKG-1042, PKG-1043, PKG-1044.
- In the exported file, change the Name column for those three rows to "Radiance Series β Standard", "Radiance Series β Premium", and "Radiance Series β Elite" respectively. Leave every other column unchanged.
- Save the file and upload it with the Validate operation. Confirm no name-conflict errors appear for any other package.
- Re-upload using Validate and Import only valid rows and click Continue.
- After the job completes, open one of the updated packages in Master data > Packages and verify the name shows "Radiance Series β Standard".
Tips
- Snapshot first. Always run the matching export before any import. A corrective import is always easier than recovering from an unwanted change.
- Small batch first. On a first-time import or after any file-format change, run 5β10 rows through Validate before the full file. Most failures surface in the first few rows.
- Verify visually. After an import, open one affected guest's package in their profile and confirm the new balance or attribute matches your expectation. Spot-checking reveals format-mismatch errors that validation may not flag.
- Time the run. Large imports process in batches and can take minutes to complete. Run during low-traffic hours if you are concerned about performance impact.
- Use Package Code as your anchor. Because the import uses Package Code as the matching key for updates, keep codes stable. If you must change a code, create a new record and retire the old one β do not reuse a code for a different package.
Troubleshooting
| Symptom | Cause and resolution |
|---|---|
| An object is missing from the second drop-down. | Permission issue β verify the object's check box under DataIO in the Administrator section of your security role (for example, CustomPackageImport for Package Balances). If the permission is present and the object is still missing, it is not enabled in your organization's import configuration β contact Zenoti Support. |
| The operation drop-down offers only Export for Bulk Package Expiry Update (Center Level). | This is expected behavior. Bulk Package Expiry Update (Center Level) is export only. To update expiry dates in bulk, use the Bulk Package Expiry Update object (which supports both import and export). |
| Import fails with "Column header mismatch" or similar. | The file's column headers don't match the expected template. Use the Download Templates link on the Import bulk data page to get the correct template, and map your data to it. |
| A Bulk Package Expiry Update row is rejected with a message about the sale date. | The new expiry date is earlier than the date the guest bought that package. Choose a date on or after the sale date. |
| A row is rejected because of a future appointment. | The guest has an appointment booked after the new expiry date. Move or cancel the appointment first, or choose a later expiry date. |
| Some rows imported and others were skipped with no error. | Rows with an empty NewExpiryDate cell are skipped rather than failed. Fill the cell, or remove the row from the import file. |
| Import fails with "Guest ID not found" on some rows. | The file references guest IDs that don't exist in this Zenoti environment. Verify the environment β exports from one environment don't import into another without ID remapping. |
| Import accepts the file but no rows change. | The import may have matched existing rows and determined no change was needed. Check the validation output for "unchanged" counts. If you expected changes, verify the value columns in your file differ from the current values in Zenoti. |
| A name-conflict error appears during Series Package or Day Package import. | The Name value in that row may already be used by a different package in the organization. Package names must be unique. Review existing package names before re-submitting β resolve conflicts in the file rather than relying on a specific import-time error message, as the package import does not enforce the same explicit duplicate-name check as some other import types. |
| Validation report shows partial success (some rows accepted, others rejected). | This is normal for large batches. Review the rejected-rows output, correct the errors in a new file containing only the rejected rows, and re-import. |
| Exported file is empty. | The export may have no data matching the current center or filter context. Confirm that the object you selected has records in this environment, then re-run the export. |
| No audit trail for who ran which import. | Bulk imports do not have a dedicated in-product audit viewer. Record operational imports through your own change-management process β attach the before and after export files to your change ticket. |