Day one — make it yours
- Set the organisation name, timezone and base currency, and be sure about the last one. Your organisation
- Upload a logo under Settings → Branding. It appears on invoices, signing envelopes and the client portal, so doing it once saves doing it three times.
- Turn on MFA for yourself before you invite anybody, so the admin account is the protected one.
- Enable only the modules you intend to use this month. You can add more in a minute; a rail with twelve icons and two in use trains people to ignore it.
Day two — bring people in
- Invite the smallest group that can complete one real workflow end to end. Two or three people beats the whole company.
- Give exactly one other person an administrator role. One admin is a single point of failure; five is nobody being accountable.
- Put everyone in Chat on day two rather than day ten — questions about the new system need somewhere to go that is not your inbox.
Days three to five — one workflow, all the way through
Resist configuring everything. Pick one thing your business does every week and do it in erp.io, start to finish, with real data. It will surface the three assumptions that were wrong, and it does that in three days instead of three months.
| If you are here for | Do this end to end | You will learn |
|---|---|---|
| Accounting | Connect a bank feed, categorise a week, reconcile it. | Whether your chart of accounts and posting rules match how you think. |
| CRM | Import 50 contacts, run one sequence, log the replies. | Whether your pipeline stages describe your actual sales motion. |
| Projects | Set up one live project with real tasks and real owners. | Whether your project shape fits portfolios or needs to be flatter. |
| Phony | Point one agent at your site, call it, read the transcript. | What the agent does not know about your business. |
| Client Portal | Put one real client in and send them one real work order. | What your clients will ask you the moment they get access. |
Northwind Trading
Week one · 6 modules enabled
18 lines unmatched
50 contacts · 12 replies
9 of 34 tasks done
Awaiting countersignature
Before you trust it
- Check a number against your old system. One figure, computed both places. If they disagree, find out why now.
- Sign out and back in as somebody else. Permissions look right from an admin account no matter how they are set.
- Read the audit log. Admin → Audit log tells you what actually happened this week, which is often not what you remember configuring.
- Find one thing that is not built. Every page in these docs carries a status badge. Knowing the edges of the product before you depend on it is worth more than any feature.
It is the most tempting thing to do and the most expensive to redo. Run the workspace on new data first, confirm the structure is right, then bring history across. Migrate covers the order.
What this does not do
A real rollout across a company is a project with a scope and a date. See By stage.
There is no separate test tenant. If you need one, make a second organisation and treat it as disposable.
Questions
Should I import everything first?
No. Structure first, data second. A migration into a wrong structure has to be done twice.
How long before the whole team is on it?
For most workspaces, two to six weeks. Roll out has the sequencing.
Who do I ask when something is unclear?
[email protected]. Include the URL you were on — it identifies the module and the screen immediately.
Related
What to actually test while evaluating erp.io, which questions separate a good fit from a bad one, and where the product is deliberately not competitive.
PilotHow to run a pilot on erp.io that produces a real decision: one team, one workflow, real data, a fixed end date, and a written verdict.