Quick answer
ERP software brings business records and processes together, such as orders, stock, approvals and reports. Before choosing it, agree how your teams work and which records are correct. Define what the first launch includes and how you will check the transferred data.
Agree the process before choosing software
Map each step from order to stock, invoice and payment where relevant. Name the person who enters or approves information and the system that holds the correct record.
Define statuses and report calculations with the teams that use them. “Completed” can mean different things to finance and operations. Use one sample task to check that everyone means the same thing.
Plan how records move to the new system
Some old data may need cleaning. Decide what must move and what can remain in an archive. Assign people to approve corrections and check imported records.
Compare agreed totals and sample records after a trial transfer. A count of imported records does not show whether stock balances or business processes are correct.
Plan the first launch and recovery
- Choose a process with named business owners.
- Agree permissions, approvals and problem cases.
- Train the staff who will use it.
- Decide how transactions entered during the move are handled.
- State which system is used until the checks are approved.
- Agree support and who can restore service if the launch fails.
What should the quote cover?
Separate the software licence from workshops, setup, custom development, record transfer, connections, testing, training and launch support. Ask what each team receives and who approves it.
A phased launch can be useful if staff know how to work during the transition. Ask the provider to explain which departments or systems depend on each other.
Your planning worksheet
Use this table to prepare the same brief for each provider. Add the person responsible and the current status for each item. Enter costs only from written quotes, in HKD, with the billing period.
| Item to plan | Details to give the provider | What to check |
|---|---|---|
| First process to launch | Process owner, correct records and dependencies | Teams agree the meaning of each status |
| Check transferred records | Imported totals, samples and correction owner | Compare agreed totals and investigate differences |
| Transition support | Training, interim process and recovery responsibility | Staff know which system to use during each phase |
Example project scenario
Illustrative planning example; not a completed customer project.
A business tries an order-to-stock process in one team. Staff agree what reserved, available and returned stock mean, then check starting records and problem transactions. A wider launch waits for the agreed checks, training and support arrangements.
Common questions
Is cleaning data the developer’s job?
Technical help can be included. Your business still needs to identify the correct records and approve changes. Assign both responsibilities.
Must every department launch together?
Not always. A staged launch must leave a workable process, with staff clear about which system to use.
What should a trial include?
A complete business task, sample records, problem cases, trained users and a recovery plan. Screens alone are not enough.
What is needed beyond software licences?
Setup, record transfer and checks, permissions, connections, training and launch support. A licence purchase alone does not cover these jobs.
Download the planning worksheet (CSV)
Find a provider through TechQuotations
TechQuotations connects Hong Kong buyers with IT service providers. Use your brief to discuss the work and compare proposals. You choose the provider and agree the terms directly. A request does not guarantee a quotation.
Explore suitable providers through TechQuotations