Is SuiteStack's ERP offering available now?

Yes. We are taking on ERP advisory, implementation and integration engagements. Get in touch and we will book a preparatory conversation about system selection, integrations and timelines.

Which business systems will you work with?

We focus on Visma and solutions across the Visma ERP portfolio, Microsoft Dynamics 365 Business Central, Oracle NetSuite and Light. The selection spans Nordic finance solutions, international group ERP and an AI-native finance platform.

Do we have to replace our ERP, or will you connect what we already have?

Both paths exist. In many cases the right answer is to keep the ERP and connect it to CRM, ecommerce and reporting instead. We always start with a mapping exercise before recommending a replacement.

How does ERP relate to HubSpot and CRM?

The ERP owns orders, inventory, invoicing and accounting. The CRM owns the relationship, the pipeline and the communication. The integration decides which system is the source for each field — so sales can see payment status and finance can see accurate customer data.

What role does Make play in an ERP integration?

Make is used when several systems need to work together with conditions, transformations and error handling without heavy custom code. When volume, security or logic goes beyond what an iPaaS platform should carry, we build a direct API integration instead.

Can we register our interest already?

Yes. Get in touch and we will book a preparatory conversation, document your system map and prioritise you in the planning ahead of the start.

Available now

The ERP is the backbone.
The connections decide its value.

Our ERP practice is now open: advisory, implementation and integration for Visma, Microsoft Dynamics 365 Business Central, Oracle NetSuite and Light. Same way of working as our CRM and automation projects — mapping first, a documented data model, and clear ownership after go-live.

We are booking preparatory conversations now.

System landscape

Conceptual illustration of a connected system landscape – not a real product interface.

Why we are opening this practice

The ERP and the CRM often live in separate realities

The companies we work with rarely have a problem with any single system. The problem sits in the gap: the same customer exists in two registers, orders and pipeline disagree, and someone has to act as a manual bridge every week.

Customer records differ between the ERP and the CRM
Sales has no visibility into order, delivery and payment status
Finance ends up in spreadsheets to reconcile
Reporting is built on exports instead of source data
Nobody has decided which system owns which field

What we build instead

A documented system map
A clear source per field and object
Order to cash as one connected flow
Integrations with logging and alerts
Assigned ownership after go-live

Platforms

Four relevant platforms and ecosystems

The selection is deliberately narrow. We would rather know four platforms properly than twelve superficially — and we will say so when none of them is the right answer for you. It does not imply any formal partnership or certification.

Focus areasVismaDynamics 365 Business CentralOracle NetSuiteLight

Visma and the Visma ERP portfolio
Visma is an ecosystem of several finance, payroll and invoicing products rather than a single platform. We work with solutions across the Visma ERP portfolio and connect them to CRM, ecommerce and reporting.
- Finance, invoicing and accounting
- Nordic bookkeeping and VAT handling
- Integration with CRM and order flows
Microsoft Dynamics 365 Business Central
Business Central suits companies already living in the Microsoft ecosystem. Finance, purchasing, inventory and projects in one platform, closely tied to Microsoft 365 and the Power Platform.
- Finance, purchasing, inventory and projects
- Close to Microsoft 365 and Power Platform
- Scales from mid-market to group level
Oracle NetSuite
Cloud group ERP for companies with several legal entities, currencies and countries. Strong when consolidation, subscription business and international reporting are core requirements.
- Multiple entities, currencies and countries
- Consolidation and group reporting
- Orders, inventory and revenue recognition
Light
An AI-native accounting and finance platform that may replace or complement parts of a traditional finance and ERP stack. Light is not a complete business system, and it is always evaluated against what you need the platform to cover.
- AI-supported accounting and finance
- Complements or replaces parts of the stack
- API-centric setup

These descriptions cover the general direction of each platform. Which one fits you depends on company structure, volume, existing systems and the processes to be supported.

Order to cash

One flow, two systems, one truth

The most valuable part of an ERP integration is rarely the technology. It is that everyone sees the same status on the same deal — from first contact to paid invoice.

Order to cash

Conceptual process flow – not a real product interface. The steps are adapted to your operation.

Customer and product data

Customer records, company registration numbers, products and price lists need an assigned source. Without one, duplicates appear the moment two departments work in parallel.

An assigned source per field
Rules for duplicates
Shared IDs across systems

Quote and order

The quote is created where the deal happens and becomes an order where fulfilment is handled. That handover should be a system step, not an email.

Quote from the CRM
Order registration in the ERP
Status returned to the deal

Invoice and payment status

When the invoice and payment status are visible in the CRM, sales stops asking finance, and finance stops answering the same question every week.

Invoicing basis
Payment status in the CRM
Reminders with context

Reporting

Reports built on source data rather than exports mean leadership can trust the numbers even when someone is on holiday.

Source data instead of exports
Defined key figures
Traceable history

Integrations

Make, APIs and native connectors

We choose the method based on volume, criticality and what you need to maintain yourselves — not on what is fastest to demonstrate.

Integration architecture

Conceptual architecture – not a real product interface. The right method depends on volume, criticality and available APIs.

Make scenarios
Make connects the ERP, CRM, ecommerce and surrounding systems with conditions, transformations and error handling. SuiteStack is a Make partner and builds scenarios that can be understood and maintained.
- Several systems in one flow
- Conditions, filters and enrichment
- Error handling and reruns
Direct API integrations
When volume is high or the logic is sensitive, we build directly against the systems' APIs, with idempotency, logging and clearly defined interfaces.
- High volume and critical flows
- Idempotency and retries
- Documented interfaces
Native connectors
If a well-maintained connector already covers the need, we use it. The simplest solution that holds up is always the first choice.
- Faster start
- Less to maintain
- Evaluated against the need
Operations and control
An integration flow is not finished when it works the first time. It is finished when someone gets an alert when it stops working.
- Logging and monitoring
- Reconciliation against source data
- Assigned ownership

Get started

What happens next

We start with a mapping exercise, document your data model and build integrations in short iterations.

Available nowWe are taking on full ERP engagements across advisory, implementation and integration.
Preparatory conversations nowWe map your system landscape and timeline so the work can start immediately.
No overstated promisesWe are clear about what we can deliver today through CRM, automation and integration — and what the ERP work adds.

ERP never stands alone

The business system becomes useful only when it talks to CRM, automation and reporting.

FAQ

What people ask us about ERP

: Yes. We are taking on ERP advisory, implementation and integration engagements. Get in touch and we will book a preparatory conversation about system selection, integrations and timelines.
: We focus on Visma and solutions across the Visma ERP portfolio, Microsoft Dynamics 365 Business Central, Oracle NetSuite and Light. The selection spans Nordic finance solutions, international group ERP and an AI-native finance platform.
: Both paths exist. In many cases the right answer is to keep the ERP and connect it to CRM, ecommerce and reporting instead. We always start with a mapping exercise before recommending a replacement.
: The ERP owns orders, inventory, invoicing and accounting. The CRM owns the relationship, the pipeline and the communication. The integration decides which system is the source for each field — so sales can see payment status and finance can see accurate customer data.
: Make is used when several systems need to work together with conditions, transformations and error handling without heavy custom code. When volume, security or logic goes beyond what an iPaaS platform should carry, we build a direct API integration instead.
: Yes. Get in touch and we will book a preparatory conversation, document your system map and prioritise you in the planning ahead of the start.

Next step

Register your interest for ERP advisory.

Tell us which business system you use today and where it hurts, and we will book a preparatory conversation.

The ERP is the backbone.The connections decide its value.

The ERP and the CRM often live in separate realities

Four relevant platforms and ecosystems

Visma and the Visma ERP portfolio

Microsoft Dynamics 365 Business Central

Oracle NetSuite

Light