Services · Migration · Modernization
CRM 4.0, 2011, 2013, 2015, AX 2009, NAV 2009, SharePoint 2010 — everything new consultants no longer know has been part of our daily work since 2007. When your old system needs to move to the cloud, we're among the few who really know both worlds.
Managing Directors · Owners
Before every migration, a fixed-price diagnostic (Migration Check or Migration Assessment). You know in advance whether the migration will be done in 6 weeks or 9 months, what it costs, and what could break. The Discovery Spike Bundle is the typical engagement bracket. Prices on request.
Department Head · Business Unit
Data audit documents that all records were migrated cleanly (with target-vs-actual comparison, GoBD-compliant gap analysis). Customization audit lists which adjustments from the legacy system were continued, replaced, or deleted — with a clear owner list per customization.
IT Lead · CIO · Solution Architect
Dynamics CRM 4.0/2011/2013/2015 → Dynamics 365, AX → F&O, NAV → Business Central, SharePoint on-prem → SharePoint Online, Exchange on-prem → Exchange Online, file server → OneDrive/SharePoint, hybrid setups. Platform-specific tooling selection (KingswaySoft, ScribeSoft, Microsoft Dataverse SDK, PowerShell migration scripts).
For Managing Directors · Migration without drama
Migration projects rarely fail on the technology — they fail because effort wasn't quantified honestly in advance. Our fixed-price diagnostic delivers, before every migration engagement, a reliable statement: duration, cost, risks, critical pitfalls. If the migration can be done in 6 weeks, we say so. If it will take 9 months, we say that too.
For Department Heads · Data audit & GoBD evidence
Migration isn't done when the new system is live — it's done when you can document in writing that nothing was lost. We deliver target-vs-actual comparison per record type, GoBD-compliant gap analysis, customization owner list, and a handover protocol that holds up in any audit. Discovery spike as a clean first engagement (price on request) with an outcome report for management and compliance.
For IT leads · Seven migration paths
Direct with the architect — no account-manager layer. Topics: plug-in re-targeting CRM 4.0/2011/2013/2015 → D365, KingswaySoft pipeline design, Dataverse batch API vs. bulk insert, AX X++ module migration to F&O, NAV AL language migration, SharePoint on-prem migration API, Exchange hybrid cut-over, ALM reset, and solution lifecycle after cut-over.
Migration types · seven paths
Seven migration paths cover the vast majority of our engagements. Each type has its own pitfalls, its own tools, and its own experience patterns.
CRM 4.0, 2011, 2013, 2015, 2016 to D365 Customer Engagement Apps. Plug-in migration, JavaScript web resources, workflow migration to Power Automate, custom-entity mapping, permission migration.
AX 2009, AX 2012 to D365 F&O. X++ code migration, forms & reports migration, data migration, custom-module assessment.
NAV versions (Navision) to Business Central. AL language migration, add-on assessment, cloud-vs-on-prem strategy, license re-modeling.
SharePoint 2010, 2013, 2016, 2019 to Microsoft 365 SharePoint. Information-architecture migration, custom web parts, workflows to Power Automate, permission model.
Hybrid or full migration. Mailbox migration, public folders, distribution lists, connector configuration, MX-record switch, hybrid-phase management.
Data from file servers to SharePoint/OneDrive (Known Folder Move, site structuring). Small custom apps to Power Apps. Permission migration via Entra ID.
Resolve half-cloud states. Full cloud architecture. Identity consolidation via Entra ID, app migration to SaaS models, legacy-system decommissioning.
Microsoft 365 tenant-to-tenant (merger, spin-off), third-party to Microsoft (Salesforce → D365, Google Workspace → M365). Please ask — chances are good we've already done it.
Diagnostics · Tier 1 before migration
Before we start the actual migration, we review three dimensions as fixed-price diagnostics. Output: you know how big the project really is — before you sign.
90-min initial conversation · free
Clarification of migration type, sizing, possible paths.
Deliverable: short memo (1–2 pages) after the conversation with effort range and recommendation for the next step.
Prices on request
Deeper assessment of the migration situation with options analysis.
Deliverables:
Prices on request
Assessment of data quality BEFORE migration. Prevents the most common migration problem: dragging junk data into the new system.
Deliverables:
Prices on request
Inventory of all customizations in the legacy system with a migration assessment per component.
Deliverable: component list with migration recommendation per component: carry over / rebuild / drop.
Price on request (Migration Assessment + Data Audit + Customization Audit combined)
Three audits in one connected discovery spike — structured, combined evaluation, shared roadmap.
When useful: for complex migrations with custom code, many data sources, or a high risk profile. Standard approach for corporate migrations.
Five migration types
Every migration starts with the honest question: where are you coming from, where do you want to go, and what data reality lies between those two points? We run five typical paths — which in practice often appear in combination.
Dynamics CRM 4.0, 2011, 2013, 2015 → Dynamics 365 Customer Engagement Apps. We know every version, every data model, every typical customization trap. Even if your on-premises installation hasn't seen a patch for eight years.
Dynamics 365 on-premises to Dynamics 365 Online, Exchange on-premises to Exchange Online, SharePoint on-premises to SharePoint Online. We've supported cloud transitions since the birth of Microsoft Azure — with a hybrid phase if needed.
You're unhappy with your current Microsoft partner — no response, no documentation, no roadmap. We take over discreetly, review the inventory, build documentation, and bring the application into a stable state.
In a merger, spin-off, carve-out, or reorganization, a Microsoft 365 tenant has to move into another: mailboxes, SharePoint, OneDrive, Teams, identities, licenses. With tools like BitTitan, Quest On Demand, or native Microsoft paths — depending on data volume and complexity.
Salesforce, HubSpot, SugarCRM, Pipedrive to Dynamics 365. Google Workspace to Microsoft 365. We know the typical data models of the third-party systems and map them onto the Microsoft data model — including custom fields, attachments, notes, and activity history.
Methodology
Every migration runs through the same methodological framework — regardless of migration type. We adapt the depth of the phases to the size and risk profile of your starting point.
Inventory of source systems: data model, customizations, plug-ins, workflows, reports, integrations, identities. We document what's usable, what gets rebuilt, what drops. Result: a migration plan with effort, risks, and corridors.
Field-by-field mapping between source and target — including transformations, lookup resolution, picklist translations, and attachments. First pilot run in the sandbox with a representative data volume. Iterate until the mapping is clean.
A rehearsed cut-over weekend with schedule, escalation paths, and abort criteria. Source system goes read-only, final data run, reconciliation reports, your sign-off, user communication. No cut-over without a successful dry run.
Daily stand-ups, fast response to findings, targeted re-migration of individual records if needed. Then transition into Application Care — no disappearing after cut-over.
Data quality
The most common mistake in migration projects: dragging along years of junk. Duplicate accounts, dead contacts, wrong addresses, records without an owner, mandatory fields with "N/A" — and everything moves unfiltered into the new system. Six months later, nobody uses it because the data feels as unreliable as in the old system.
In the audit we run a data-quality sample: duplicate rate, completeness of mandatory fields, plausibility of values, currency (last modified), orphans (records without an owner or relationship). This sample is the basis for the migration strategy.
Option A — take everything along: cheapest migration path, but the problem comes along. We only recommend this when the source system is already very clean or when regulatory reasons require it.
Option B — cleanup in the source system before migration: you clean with your users, who know the business. We provide reports and tools for it. Effort for you, but the best result.
Option C — cleanup in the mapping: we define rules (e.g., "records without activity in 36 months land in an archive container") and apply them in the mapping. Faster than Option B, but rules must be very clear, otherwise the wrong records disappear.
A migration is always a data inventory. Use it — the second-best time to improve data quality is the next migration in ten years.
After the migration
A migration is more than copying records. It's the rare opportunity to dock a stack from a different era to today's Microsoft world — Power Platform, Microsoft 365 Copilot, Dataverse integration, modern security and compliance paths. We take this chance where it brings value.
Concretely: old JavaScript scripts become Power Automate flows; old SSRS reports become Power BI dashboards; old plug-ins become custom connectors or Azure Functions; old workflows become modern business process flows. Not everything has to be new — but the aging of the solution doesn't begin in five years; it's decided in the migration itself.
After cut-over, the application moves into our Application Care flat rate — second- and third-level support, release maintenance, continuous optimization. The migration is not the endpoint but the start of a new lifecycle phase.
Frequently asked questions
Duration depends on the migration type and data volume. A version upgrade from Dynamics CRM 2015 to Dynamics 365 without major customization changes typically takes 2–4 months. On-premises to cloud with mid-range data volume runs 3–6 months. Microsoft 365 tenant-to-tenant depends on mailbox and SharePoint data volume — 6 weeks to 6 months. Partner change without technical migration is a matter of handover depth and typically runs 4–8 weeks. We set the precise size in the migration check.
Data loss is ruled out with a cleanly planned migration — mapping, multiple test runs in sandbox environments, and reconciliation reports before and after cut-over make every row traceable. Customizations are the real challenge: old JavaScript scripts, plug-ins, and reports don't run 1:1 on Dynamics 365. In the audit we review what has to be rebuilt technically, what can be replaced by standard features, and what can be dropped because nobody has used it for years.
Old SSRS and FetchXML reports from Dynamics CRM on-premises can sometimes be ported to Dynamics 365 — we review each report individually and decide together with you: port, rebuild in Power BI, or drop. In our experience 30–50 percent of old reports are still actively used; the rest are dead files. Power BI doesn't replace every SSRS report, but it covers modern reporting much more broadly.
The partner change itself doesn't cost any license fee — CSP re-assignment is administrative. Effort arises for the handover phase: inventory audit, documentation build-up (if none exists from the predecessor), knowledge transfer, reconnecting ALM pipeline and backup strategies. Prices on request — we calculate effort for a clean handover after intake in the migration check. Discretion and data protection are guaranteed throughout the process. Details on CSP handover can be found under License Advisory.
Classic Dynamics CRM workflows can partly be ported to Power Automate, partly have to be rebuilt. In the audit we analyze each workflow, review trigger logic, actions, and branching conditions, and decide: Power Automate flow, Dynamics 365 Business Process Flow, plug-in, or drop. Here too: old workflows often carry logic from a time when the process ran very differently. Migration is a good opportunity to review this logic critically.
Take-away · two materials
Two depths for different reading needs. The factsheet is a quick reference (3–5 min) and instantly downloadable. The whitepaper is market education with methodology and comparison data (15–30 min) — you get it by email after a short request.
3–5 min read · Direct download · no form
Compact overview: scope, key metrics, pricing model, process — ideal to forward to CFO, procurement, or the business unit.
15–30 min read · by email after request
Methodology, comparison data, recommendation framework — material for internal argumentation toward stakeholders.
Related services
License migrations — from the old provider to the arades CSP, with renewal optimization.
Read more →
Data migration with a defined mapping and cut-over strategy.
Read more →
When the migration is part of a larger implementation project.
Read more →
Complete inventory as the basis for migration planning.
Read more →
Migration check
30-min initial conversation — free migration check. We review your starting point, sketch the right migration path, and call out the typical pitfalls openly. You get a candid assessment and a discovery proposal, usually quickly. On request we hand off directly into our other services.
Take-away
Two-page quick reference with package structure, delivery areas, and three reasons for arades — instantly downloadable, no form. Ideal to forward to CFO, procurement, or the IT lead.
3–5 min read · Direct download · no form
