A colder, sharper redesign of the Nexus page inspired by the current SpaceX and xAI/Grok visual language: monochrome contrast, oversized typography, restrained blue light, and motion that feels deliberate instead of decorative.
Normec Group operates more than forty separate Exact Online administrations. The requirement is not just to migrate them into Dynamics 365 Business Central, but to keep both worlds aligned while cutover is still ahead.
Each company carries its own chart of accounts, master data, journals, historical postings and local accounting realities. Doing that by hand turns into a slow consulting project.
This is not a one-off load. New sales, purchases, bank movements and memorial entries continue to land in Exact and need to show up in BC without manual intervention.
Teams can keep working in Exact while BC is trained, loaded and validated in parallel. When the switch happens, BC is already a current mirror of operations.
The core loop is straightforward: Exact remains the source, Nexus orchestrates state and replay, and Business Central receives validated journal traffic in the structure it expects.
Exact Online
Source system for divisions, journals and master data
Business Central
Target platform for posted journals and operational cutover
Each transaction class has its own processing rules, but the orchestration is shared: extract, stage, validate, apply bookkeeping rules, then post into the right BC journal route.
Before live sync begins, each administration goes through a fixed migration order so setup, balances and historical movements enter BC in a coherent way.
| Step | Phase | Purpose | Output |
|---|---|---|---|
| 01 | Extract | Pull entities, dimensions, master data and journal history from Exact. | Raw migration package |
| 02 | Create | Provision BC company and baseline environment for the target entity. | Ready company shell |
| 03 | Configure | Load setup, RapidStart templates, posting groups and local defaults. | Config-complete tenant |
| 04 | Map | Transform source structures into BC-compatible shapes and sequences. | Posting-ready payloads |
| 05 | Validate | Check balances, VAT behavior, dimensions and ledger consistency. | Verified migration set |
| 06 | Load + Sync | Replay the migration package and activate ongoing incremental sync. | Live BC mirror |
The first company is fully migrated and reconciled. This section is framed like a mission results board rather than a conventional dashboard card stack.
The engine is not a one-company script. It is a repeatable factory: feed it a division, configuration and rollout order, then let it execute the same migration logic at scale.
Core engine and processing logic.
Serverless execution layer.
Workflow orchestration and retries.
Source extraction and delta sync.
Target loading and updates.
Business Central staging and posting.
Sync state and watermarks.
Monitoring and progress visibility.
BC can already stay warm and synchronized while Exact remains operational. Final cutover becomes a controlled last sync instead of a risky migration weekend.
AWS BV is complete. The remaining companies can now be ordered by country, legal complexity, volume or operational readiness.
The engine is repeatable. Once the production BC environment is ready, the same migration path can be executed again with production targets.
Running every 15 minutes is straightforward. The question is when to enable group-wide cadence and which entities should enter the live schedule first.