Importing legacy data

In most cases, legacy data import all cases will require writing custom code to deal with your particular legacy data. The example scripts here will not work "out-of-the-box". Importing your legacy data will most probably involve some hacking on the example scripts noted below. Contributions to the import process are welcome.

bin/bind.import - Import domain information from BIND named
bin/passwd.import - Just import `passwd' and `shadow' or `master.passwd', no RADIUS import.
bin/svc_acct.import - Import `passwd', ( `shadow' or `master.passwd' ) and RADIUS `users'. Before running bin/svc_acct.import, you need services (with table svc_acct) as follows:
- Most accounts probably have entries in passwd and users (with Port-Limit nonexistant or 1)
- Some accounts have entries in passwd and users, but with Port-Limit 2 (or more)
- Some accounts might have entries in users only (Port-Limit 1)
- Some accounts might have entries in users only (Port-Limit >= 2)
- POP mail accounts have entries in passwd only, and have a particular shell.
- Everything else in passwd is a shell account.
bin/svc_acct_sm.import - Import qmail ( `virtualdomains' and `rcpthosts' ), or sendmail ( `virtusertable' and `sendmail.cw' ) files. Before running bin/svc_acct_sm.import, you need services as follows:
- Domain (table svc_acct)
- Mail alias (table svc_acct_sm)
Importing customer data
- Manually
  - Add a new customer
  - Add one or more packages for this customer
  - Enter a package by clicking on the package number
  - Pick the `Link to existing' option
- Batch - You will need to write a script to import your particular legacy data. You can use eg/TEMPLATE_cust_main.import as a starting point.