An import changes many production records at once, so analysis, review and execution are separate. API integrations should likewise be verified on a small controlled set before scheduled synchronization.
Before you begin
- Keep an unchanged backup of the source file.
- Create target locations and normalize model names first.
- Choose a unique identifier, usually serial number.
Analyze first
Upload CSV for analysis first. Printexus validates required fields, serial numbers, locations and conflicts before import.
Large batches
Processing runs in batches with progress. Follow the job and download errors instead of rendering thousands of rows.
API and Kyocera
Store integration credentials only in the secured module, never in ticket notes or public documentation.
Recommended practice
- Run the first import on a few rows and inspect Printer 360.
- Fix rejected rows at source instead of repeated manual edits.
- Limit integration credentials to necessary operations.
Common pitfalls
- Reimport without identifier checks may create conflicts.
- Location spelling differences may create separate objects.
- Never send API keys in ordinary tickets or email.
How to verify the result
Devices land in correct locations without duplicates and integration behavior remains predictable and auditable.
✓
Continuously updated for the current Printexus release.
Still need help? Contact support.