Implementation
An implementation moves an organization from its previous system to operating in Netzo. The quick start configures the organization; this page puts the full project in order around it.
Discover
Map the business to the Netzo model: which legal companies, sites and teams there are, which modules each area uses and which tables hold their data. Write down who approves what: these become the roles and the approvals.
Configure
Follow the quick start: structure, modules, roles, people, master data and settings. For Mexico, load the digital seal certificates of each company and its tax data. Review the document templates with the customer.
Migrate
Load the data from the previous system in this order, because each one points to the one before it:
- Master data: customers, suppliers, products, services, employees.
- Opening balances: stock per warehouse, bank accounts, customer and supplier balances, accounting balances.
- Open documents: orders, purchase orders and invoices that are still open.
With an AI assistant, use the netzo-mcp-import skill: it reads each table, orders the loads by references, finds the records that already exist and does a dry run of each row before it saves it. With a program, use the API.
Test
Test the processes end to end with the people who will do them: from quote to cash, from requisition to payment. Use a dry run to see what an action would do without saving, and can to check that each role has what it needs and nothing more.
Go live
Choose a cutoff date. Freeze the previous system, load the final balances and movements at that date and start to operate in Netzo. From then on, Netzo is the system of record.
Operate
Review the activity log and the approval requests in the first weeks. Connect your systems with webhooks and the API, and give the teams skills for their repeated tasks: reconcile banks, close the month, process orders.