Skip to main content

​
Move subscriber data safely

Use Subscribers → Import / export for controlled bulk onboarding, migration, or reporting. The application supports a downloadable template, parse/preview, final import, MikroTik preview/import, and filtered export.

​
Before importing

  1. Create and verify packages and routers first.
  2. Export the current subscriber list as a rollback/reference snapshot.
  3. Start with a small representative file.
  4. Normalize user types to supported values.
  5. Match package names exactly to current compatible packages.
  6. Use unambiguous usernames, account numbers, phones, emails, and MACs.
  7. Remove formulas and unexpected formatting from spreadsheet exports.

​
Standard import

1

Download the current template

Use the template provided by this version rather than an older spreadsheet. Column names and supported values can change.
2

Prepare the file

Keep one subscriber per row. Preserve the header. Use explicit text formatting for phone numbers, account numbers, usernames, and MAC addresses so spreadsheet software does not alter them.
3

Parse and preview

Upload the file and inspect row-level validation. Correct errors in the source file; do not ignore a mismatch simply because other rows are valid.
4

Import a small batch

Complete the import, then verify several profiles, package assignments, expiry values, and access records.
5

Import the remaining approved data

Keep the result summary and do not upload the same file again until duplicate behavior is understood.

​
MikroTik import

The MikroTik path previews users discovered from router context before importing. Confirm the router, service type, package mapping, and duplicate strategy. A router username is not automatically the same person as an existing application subscriber—match deliberately.

​
Export

Choose the required scope and columns, apply filters, review the count, and generate the export. Exported files can contain personal and network data; store them with access controls and delete temporary copies when the task is complete.

​
Common import failures

  • Unknown package: create/correct the package or fix the exact name.
  • Wrong type: use a supported subscriber type and compatible package.
  • Duplicate username/phone/email/MAC: search the existing subscribers and update the intended record instead of cloning it.
  • Invalid date/time: use the format required by the current template and confirm timezone.
  • Missing binding NAS/MAC/IP: supply the full binding context.
  • Partial success: use the result summary to identify created versus rejected rows before retrying.