Acumatica· Implementation plan
Step 1 of 11 · Pre-implementation · Updated October 26, 2026

Acumatica implementation plan

A Acumatica implementation plan turns the statement of work into tasks with owners, dates and dependencies. Most of the risk in a Acumatica project is decided here: the structure, the scope of history, and who owns the data cleanup. superglue's agent drafts the plan from your kickoff documents and keeps it in a project that every later step reuses.

How this step works

What the agent does

  • Reads the statement of work, kickoff notes and uploaded exports, and extracts scope, entities and milestones.
  • Drafts tasks with owners, due dates and dependencies, grouped by workstream.
  • Turns open questions into client tasks, so blockers are visible early.
  • Keeps the project context, so later sessions know the client, the systems and the decisions already made.

What you decide and approve

  • The scope of the engagement and what is out of scope.
  • Owners, dates and the milestones the client signs.
  • Which playbook the project follows, built-in or your firm's own.

What the client gets

  • A project plan with tasks, owners, dates and dependencies.
  • A list of open questions and the client tasks that unblock them.

What to get right in a Acumatica plan

  1. 01

    Design subaccounts with restraint

    The most expensive Acumatica mistake is a subaccount structure built like a legacy account string. Most other configuration mistakes are quick to fix. This one stays for years.

  2. 02

    Decide companies and branches first

    They decide where balances live and how the client reports. Master data and balances depend on them.

  3. 03

    Let the client own the project

    Name a subject-matter owner on the client side for each area. Projects where the client only reviews take longer.

From Acumatica partners
18
ERP implementation firms in Pine Services Group
10,000+
customers served by those firms

Through Pine Services Group, work is underway with i-Tech, an Acumatica partner.

Read the announcement

Frequently asked questions

What should a Acumatica implementation plan decide first?

Design subaccounts with restraint; Decide companies and branches first; Let the client own the project. These decisions shape every later step, so they belong in the plan.

Can the agent build the plan from our existing documents?

Yes. Upload the statement of work and kickoff notes, or connect the drive, Slack or Teams channel where they live. The agent drafts the plan and asks only where a business decision is missing.

How does superglue work with our consultants?

superglue works alongside your team. The agent takes on the repetitive work, such as reading documents, drafting, mapping, loading and reconciling. Your consultants keep the client relationship and the decisions, and they approve every change to a client system.

Can we use our own implementation method?

Yes. Write your firm's method as a playbook, and every consultant and every session follows it. The documents the agent produces carry your firm's branding.

Which systems can we migrate from into Acumatica?

Common sources are Microsoft Dynamics GP, QuickBooks, Sage 100, MYOB and spreadsheets. The agent also reads Excel, CSV and XML exports and most systems with an API or a database.

Is client data safe?

superglue holds a SOC 2 Type 2 report and works under GDPR. Credentials are encrypted with AES-256. On the Enterprise plan, superglue can run on your own infrastructure.

How do we start?

Start with one live Acumatica project. Connect the client's systems, give the agent the statement of work, and run the first steps together with us.