A useful place
to get started.

A good evaluation follows a real transaction from beginning to end. Choose one representative process rather than trying to cover every possible feature at once.

1. Choose a common sale, purchase or service project. Describe the people involved and the records each one needs.
2. List the handoffs that currently require re-entry, messaging or reconciliation.
3. Bring anonymised examples of document fields and approval requirements. Do not share confidential customer data.
4. Ask to see the actual workflow, optional add-ons and any limitations before deciding.

Connected software works best when shared records are consistent. Before migration, review the master data that appears in daily transactions.

1. Deduplicate customer and vendor names. Check contact details and applicable business identifiers.
2. Review item codes, units and warehouse naming so the same goods are not represented differently across files.
3. Identify opening balances and the date you intend to begin working in the new system.
4. Confirm supported import formats and responsibilities with the team. Keep original exports and let your accountant review financial opening data.

Start from responsibilities, not job titles alone. A person who prepares invoices may not need access to employee records or organisation settings.

1. List who creates, reviews and administers records in each workflow.
2. Map those responsibilities to the module and action permissions available in Scalar360.
3. Review access when someone joins, changes role or leaves.
4. Confirm your export, audit and retention requirements during setup.

For product questions, share a short description of the issue, the relevant workflow and what you expected to happen. Avoid sending passwords or sensitive business records.

For plan comparisons, use the calculator to see users, add-ons and GST. For a process-fit question, ask the team to demonstrate the exact handoff you need.