System Import
The System Import Page is a centralized interface for uploading and importing various types of data into the Stripes system. It provides three main import capabilities: restoring project backups, importing project data, and uploading match databases.
Overview
The page displays three independent import sections side-by-side (stacked on mobile):
- Left: Restore Backups
- Center: Import Projects
- Right: Match Databases
Each section operates independently with its own upload controls and job lists.
Download file if needed for backup and delete uploaded file if no longer needed, to save disc space.
Features
Restore Backups
Restore complete project backups to recover from data loss, migrate systems.
Upload Backup File
- Click "Browse" button
- Select backup file from your computer
- File Type: ZIP archive (
.zip) - Contents: Full project backup created from Export page
- File Type: ZIP archive (
- Upload begins automatically
- Progress bar displays upload percentage
- File appears in list when upload completes
- If warnings appear, review logs to determine if action needed
Import Projects
Batch project creation by importing projects from external file.
Upload Project File
- Click "Browse" button
- Select project import file
- Upload begins automatically
- Progress bar displays upload percentage
- File appears in list when upload completes
- If warnings appear, review logs to determine if action needed
Check the import logs. The Branch and Project values gettting validated by RegEx validations from the settings. If you have repeated blocked imports, please contact your System-Admin
File Format
A project gets unique by the combination of client code, branch code and project code.
Optional columns should be removed if not used.
The file has do be a comma separated CSV file. Download an Example File
| File Header | Description | Status | Remarks |
|---|---|---|---|
| client.code | The code of an existing Client | required | If the Client with this code do not exist the import of this row fails |
| branch.code | Code of the beloning branch | required | If the branch do not exist the branch will be created -> in this case the branch name is required |
| branch.name | Name of the branch | optional | Branch Name is only required if the branch with the given branch code do not exist |
| project.code | Code identifier of the project | required | Code identifier of the project |
| projcet.name | Name of the Project | required | Name of the Project |
| project.effectiveDate | The effective date from the ERP system | required | Format YYYY-MM-DD |
| project.startDate | The actuall start date and time | required | Format YYYY-MM-DDTHH:MM:SS+HH:MM The date and time is saved in UTC and it requires the time difference of the destination country. |
| project.endDate | The expected end date and time | required | Format YYYY-MM-DDTHH:MM:SS+HH:MM The date and time is saved in UTC and it requires the time difference of the destination country. |
| project.misc.crm | The ERP referance number | required | Cost center reference from the ERP/CRP System |
| project.teamManager | User Name of the Team-Manager | optional | Expects the username of the associated team-manager. The User will be automatically registered on this project |
| project.projectManager | User Name of the Project-Manager | optional | Expects the username of the associated project-manager. |
| project.teamId | Internal ID of the belonging Team | optional | Expects the internal ID of the associated team. |
Match Databases
Upload SQLite databases containing reference inventory data for scan matching and verification. This feature is only used in edge cases. Consider the proper match import from the project import page
Upload Database File
- Click "Browse" button (only visible with permission)
- Select database file
- File Type: SQLite database (
.sqlite) - Contents: Match data (barcodes, descriptions, counts, etc.)
- File Type: SQLite database (
- Upload begins automatically
- Progress bar displays upload percentage
- File appears in list when upload completes
- If warnings appear, review logs to determine if action needed
Database Requirements:
- Must be valid SQLite format
- Required schema/tables must exist toDo Link to the technical documentation about the sqlit schema
- Data types must match expectations
- Large databases may take longer to import
Import Behavior:
- New data may replace or merge with existing
- Duplicate handling depends on configuration
- Import validation prevents corrupt data
- Errors logged for troubleshooting
Performance:
- Large databases (>100MB) may take significant time
- System performance may be impacted during import
- Consider off-hours for large imports
- Monitor system resources
Visual Indicators
Job Status Icons
| Status | Icon | Color | Description |
|---|---|---|---|
| Running |  | Grey | Job in progress Do not cancel unless necessary |
| Completed |  | Green | Successfully finished |
| Warning |  | Orange | Job completed but with issues Check logs for details Verify results |
| Failed |  | Red | Error occurred Check logs for details |
| Cancelled | | Orange | User cancelled |
| Waiting |  | Grey | Queued for execution Will start automatically |
Troubleshooting
- Can't see one of the import categories
- Check the permissions and contact your System-Admin
| Role | Access |
|---|---|
| System-Admin | all sections |
| Admin | Project Import Match Databases |
| User-Admin | Project Import Match Databases |
| Team-Admin | Project Import Match Databases |