CRM migration

Migrate from Jonas Enterprise Service & Construction Software to Microsoft Dynamics 365 Sales

Field-level mapping, validation, and rollback between Jonas Enterprise Service & Construction Software and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .

Jonas Enterprise Service & Construction Software logo

Jonas Enterprise Service & Construction Software

Source

Microsoft Dynamics 365 Sales

Destination

Microsoft Dynamics 365 Sales  logo

Compatibility

100%

12 of 12

objects map 1:1 between Jonas Enterprise Service & Construction Software and Microsoft Dynamics 365 Sales .

Complexity

BStandard

Timeline

2–4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Jonas Enterprise Service & Construction Software stores construction-specific data—job costing, work orders, equipment, service agreements, and payroll tied directly to projects—in a SQL Server-backed ERP that runs on-premise or Jonas Cloud (Azure-hosted). Dynamics 365 Sales operates on Microsoft Dataverse with standard CRM entities: Account, Contact, Lead, Opportunity, Case, and Product. There is no native one-to-one entity for Jonas's construction job structure, so FlitStack AI maps Jobs to a combination of Opportunities with custom fields capturing job-cost segments (labor, materials, subcontractor), and Jonas service agreements migrate as custom Agreement__c records linked to Accounts. The migration carries Jonas customers, contacts, equipment records, work orders, service tickets, and active job data into Dynamics 365 Sales. Jonas workflows, service-agreement logic, payroll integrations, and equipment-maintenance schedules do not migrate—they must be rebuilt in Dynamics using Power Automate flows, field-service scheduling, and the built-in Asset management entity. We extract Jonas data via SQL views against the Jonas database (for on-premise) or Jonas API exports (for cloud), validate against the Jonas schema, then load into Dynamics via the Dataverse Web API with parallel processing to handle volume efficiently. Original Jonas record IDs are preserved in Dynamics as Source_System_ID__c for traceability and delta-run deduplication. A delta-pickup window captures any records modified in Jonas during the cutover, typically 24–48 hours, so Dynamics reflects the final state of active projects and open service tickets at go-live. One-click rollback is available if reconciliation fails.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Jonas Enterprise Service & Construction Software logo

Jonas Enterprise Service & Construction Software

What's pushing teams away

  • No public API — multiple reviewer aggregators note that Jonas Construction Software does not expose an open API, while ServiceTitan offers 30+ direct open API integrations. Customers wanting real-time data sync hit this wall hard.
  • Mixed UX reviews — some reviewers describe the system as not user-friendly and call out overcomplicated housekeeping procedures that force extra headcount to maintain.
  • Implementation cost is significant — Premier Starter implementation alone is $15,000 plus $249/user/month; Premium $25,000 + $149/user; Enterprise $50,000 + $125/user. Buyers underestimating implementation fees often migrate away.
  • Integration ecosystem is narrow versus competitors — Capterra/G2 reviewers note 11 documented integrations versus ServiceTitan's 56, and the project-management side of construction is not natively connected.
  • Windows-client architecture on top of SQL Server feels dated next to modern SaaS-native competitors with browser-based UX and mobile-first design.

Choosing

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

What's pulling them in

  • Deep Microsoft 365, Teams, and Outlook integration makes Microsoft Dynamics 365 Sales a natural fit for Microsoft-first organizations already invested in that ecosystem
  • Sales Enterprise and Premium tiers offer unlimited custom tables and advanced AI-driven forecasting and predictive analytics not available in lower tiers
  • Professional tier pricing at $65 per user per month offers a lower entry cost than Salesforce for SMB teams with straightforward CRM needs
  • Flexible customization options allow businesses to build bespoke apps, tailor forms and views, and integrate with other Dynamics 365 modules
  • Microsoft Copilot AI tools are embedded directly into the sales workflow on Enterprise and Premium, automating routine tasks and providing deal intelligence

Object mapping

How Jonas Enterprise Service & Construction Software objects map to Microsoft Dynamics 365 Sales

Each row shows how a Jonas Enterprise Service & Construction Software object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Jonas Enterprise Service & Construction Software

Customer

maps to

Microsoft Dynamics 365 Sales

Account

1:1
Fully supported

Jonas 'Customer' is a company-level record storing name, address, billing terms, and credit limits. Maps directly to Dynamics Account via FlitStack AI field mapping. Jonas Customer records containing multiple contacts collapse to a single Account with multiple Contact records linked via the AccountId lookup relationship. When migrating, the Jonas CustomerID is preserved as Source_System_ID__c on the Dynamics Account for traceability and deduplication during subsequent delta runs.

Jonas Enterprise Service & Construction Software

Contact

maps to

Microsoft Dynamics 365 Sales

Contact

1:1
Fully supported

Jonas Contact stores individuals linked to a Customer with fields for name, email, phone, role, and the customer they belong to. Maps directly to Dynamics Contact. The Contact.AccountId lookup is resolved from the associated Jonas Customer before migration so foreign-key integrity holds in Dynamics.

Jonas Enterprise Service & Construction Software

Job / Project

maps to

Microsoft Dynamics 365 Sales

Opportunity

1:1
Fully supported

Jonas Job is a construction project record with phases, cost codes, WIP tracking, and budget vs. actual labor/materials/subcontractor segments. There is no direct Opportunity equivalent, so FlitStack AI creates a Dynamics Opportunity for each Jonas Job and populates custom fields for Job_Number__c, Contract_Type__c, Budget_Labor__c, Budget_Materials__c, Budget_Subcontractor__c, and WIP__c from the Jonas job-cost breakdown.

Jonas Enterprise Service & Construction Software

Work Order

maps to

Microsoft Dynamics 365 Sales

Case

1:1
Fully supported

Jonas Work Order tracks service requests with status, priority, assigned technician, line items for parts, and labor hours. Maps to Dynamics Case with custom fields for Work_Order_Number__c, Technician__c, and Labor_Hours__c. Open work orders migrate as active Cases; completed work orders migrate as resolved Cases with closure dates preserved.

Jonas Enterprise Service & Construction Software

Service Agreement / PMA

maps to

Microsoft Dynamics 365 Sales

Agreement__c (Custom)

1:1
Fully supported

Jonas Preventive Maintenance Agreements (PMAs) define recurring service contracts tied to customer equipment with billing frequency and scope of work. Dynamics has no native service-agreement entity, so FlitStack creates an Agreement__c custom table with fields for Agreement_Number__c, Customer__c (lookup to Account), Equipment__c (lookup to Asset), Billing_Frequency__c, and Scope_of_Work__c.

Jonas Enterprise Service & Construction Software

Equipment / Asset

maps to

Microsoft Dynamics 365 Sales

Asset (Field Service)

1:1
Fully supported

Jonas Equipment records store make, model, serial number, location, and maintenance history. Maps to Dynamics Asset entity when Dynamics 365 Field Service is licensed. Standalone Dynamics 365 Sales without Field Service requires a custom Asset__c table—your license tier determines the target entity.

Jonas Enterprise Service & Construction Software

Inventory / Parts

maps to

Microsoft Dynamics 365 Sales

Product

1:1
Fully supported

Jonas Inventory tracks parts and materials with part numbers, descriptions, unit costs, and warehouse locations. Maps to Dynamics Product with Name, Product Number (Jonas part number), and Standard Cost (Jonas unit cost). Jonas inventory warehouses do not map to Dynamics—warehouse tracking requires a separate inventory management solution or Dynamics 365 Supply Chain Management.

Jonas Enterprise Service & Construction Software

Quote / Proposal

maps to

Microsoft Dynamics 365 Sales

Quote / Opportunity Product

1:1
Fully supported

Jonas Quote records store quoted amounts with line items for labor and materials tied to specific jobs. Migrates to Dynamics Quote entities linked to the corresponding Opportunity (mapped from the Jonas Job). Quote line items map to Opportunity Product records with Unit Price from the Jonas quote amount and Quantity representing the estimated unit count.

Jonas Enterprise Service & Construction Software

Employee

maps to

Microsoft Dynamics 365 Sales

SystemUser

1:1
Fully supported

Jonas Employee records contain payroll data, certifications, union status, and field-time assignments. Payroll does not migrate to Dynamics 365 Sales—Employee records map to Dynamics SystemUser only for users who will have Dynamics licenses, with Payroll_Employee_ID__c stored as a custom field for reference. Unlicensed employees are not created as Dynamics users.

Jonas Enterprise Service & Construction Software

Document

maps to

Microsoft Dynamics 365 Sales

SharePoint / Note

1:1
Fully supported

Jonas Documents stores project files, drawings, and client communications linked to Jobs, Customers, or Work Orders. Files migrate to SharePoint Document Libraries connected to the corresponding Dynamics Account or Opportunity. Jonas document metadata (document type, created date, author) is preserved as Note records in Dynamics pointing to the SharePoint file location.

Jonas Enterprise Service & Construction Software

Payroll / Time Entry

maps to

Microsoft Dynamics 365 Sales

None

1:1
Fully supported

Jonas payroll, direct deposit configurations, union payroll rules, certified payroll, and time-entry uploads do not migrate. Time-entry data for active Jobs is not a standard Dynamics 365 Sales object—payroll remains in Jonas or moves to a separate Dynamics 365 Finance instance. We flag which Jonas employees have Dynamics user licenses so Jonas payroll can be reconciled against the corresponding SystemUser records post-migration.

Jonas Enterprise Service & Construction Software

Workflow / Automation

maps to

Microsoft Dynamics 365 Sales

Power Automate / Power Apps

1:1
Fully supported

Jonas workflow rules, email triggers, approval chains, and automated service-dispatch logic are platform-specific and do not export. FlitStack AI provides a Jonas Workflow Export documenting each rule's trigger, condition, and action so your Dynamics admin can rebuild equivalent Power Automate flows. Jonas's J-Mail email integration requires SMTP relay reconfiguration in Microsoft 365.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Jonas Enterprise Service & Construction Software logo

Jonas Enterprise Service & Construction Software gotchas

High

No public REST/Bulk API for data export

High

Payroll-to-job-cost link must be explicitly mapped

Medium

Multi-company structures fragment customer and vendor IDs

Medium

Documents reference network file paths or database BLOBs

Low

Jonas Forms cannot be migrated to non-Jonas systems

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales gotchas

High

Professional tier 15-table custom table limit blocks migrations

High

October 2024 pricing increase applies at renewal for all customers

Medium

Custom fields must be created in the UI before API writes

Medium

Power Platform request limits apply to bulk migrations

Medium

Activity records orphaned to inactive owners fail silently

Pair-specific challenges

  • Jonas Jobs require custom Opportunity fields that Dynamics Sales Professional limits

    Dynamics 365 Sales Professional license caps custom tables at 15—Job_Number__c, Contract_Type__c, Budget_Labor__c, Budget_Materials__c, Budget_Subcontractor__c, WIP__c, and Source_System_ID__c alone consume six slots. Teams with additional custom fields ( Jonas-certified payroll class, union craft codes, Davis-Bacon prevailing wage flags) can exceed this limit on Sales Professional. FlitStack AI audits all custom field requirements during discovery and flags whether your license tier requires a Sales Enterprise upgrade before the migration plan is finalized.

  • Jonas multi-company setups create duplicate Account records in Dynamics

    Jonas supports multi-company/subledger configurations where one legal entity operates as multiple Jonas companies sharing a database but with separate customer and job namespaces. When these customers map to Dynamics, FlitStack AI must deduplicate by TaxID/EIN—if two Jonas companies share the same customer (e.g., a parent LLC and a subsidiary project company), they collapse to a single Dynamics Account. If the businesses are genuinely separate legal entities with different TaxIDs, they create separate Dynamics Accounts. We surface this mapping decision before migration runs so your team can confirm the collapse rule.

  • Jonas service agreements need manual rebuild as Dynamics Field Service Agreements

    Jonas Preventive Maintenance Agreements (PMAs) define recurring service scopes, billing intervals, and equipment linkages that are deeply integrated with Jonas job costing and payroll. Dynamics 365 Field Service has an Agreement entity, but it operates on the Field Service scheduling board and Asset lifecycle model—not Jonas's job-cost posting model. FlitStack migrates PMA data as Agreement__c records (custom table) for reference, but the recurring billing logic, service-interval triggers, and technician dispatch rules must be rebuilt in Dynamics Field Service by your admin after migration. We provide a PMA export document listing every agreement's scope, frequency, and linked equipment.

  • Jonas on-premise SQL exports require a dedicated migration window

    Jonas Cloud customers can use Jonas API endpoints for extraction, but Jonas on-premise deployments require FlitStack AI to connect directly to the Jonas SQL Server database with read-only credentials to generate export views. This requires your Jonas DBA or IT team to grant SELECT access on Jonas tables, expose the database to the FlitStack migration environment (VPN or firewall rule), and coordinate the export timing with your Jonas update schedule. Jonas's SQL schema is not publicly documented—FlitStack reverse-engineers table relationships from the Jonas ERD, which adds 3–5 business days to the discovery phase for on-premise deployments.

  • Jonas email relay deprecation requires Microsoft 365 SMTP reconfiguration

    Jonas email functions currently use Basic Auth against Microsoft Office 365 SMTP relay, which Microsoft is disabling in December 2026. After migrating to Dynamics 365 Sales, any Jonas-integrated email workflows (J-Mail notifications, Jonas Documents email triggers) will stop working unless reconfigured. FlitStack AI does not migrate Jonas SMTP settings—these must be re-established in Microsoft 365 by your IT team using OAuth 2.0 authentication. We document every Jonas email trigger and notification that relied on SMTP relay so your team can rebuild them as Power Automate cloud flows or Dynamics email templates post-migration.

Migration approach

Six steps for a successful Jonas Enterprise Service & Construction Software to Microsoft Dynamics 365 Sales data migration

  1. Discovery and Jonas schema profiling

    FlitStack AI connects to your Jonas database (SQL for on-premise, API for Jonas Cloud) and profiles the schema to identify all active tables: Customers, Contacts, Jobs with cost-code segments, Work Orders with labor lines, Equipment, Inventory, Service Agreements, and Documents. We generate a Data Profile Report listing record counts per entity, blank field rates, and duplicate candidates. For multi-company Jonas setups, we identify shared customers that will collapse to single Dynamics Accounts. This phase produces the field-mapping specification signed off before any data movement begins.

  2. Design Dynamics custom schema and license check

    We audit your Dynamics 365 Sales license tier (Professional vs. Enterprise) against the custom field count required by the Jonas migration. For every Jonas custom property (contract type, union craft code, WIP segment) that needs a Dynamics custom field, we verify it fits within the license cap. If Sales Professional's 15-table limit is insufficient, we recommend the Enterprise upgrade path before migration. Your Dynamics admin creates the custom Opportunity fields, the Agreement__c table (if Dynamics Field Service is not licensed), and the Source_System_ID__c fields across entities—FlitStack provides the exact schema specification.

  3. Resolve owners and user mapping

    Jonas technician assignments on Work Orders and Jonas project managers on Jobs map to Dynamics SystemUsers. FlitStack AI resolves each Jonas user by email address against your Dynamics 365 tenant—matched users get their records assigned to them; unmatched users are flagged for your admin to create Dynamics accounts or assign to a fallback owner. Jonas employees who are not Dynamics license holders (e.g., field-only staff on Jonas payroll) are not created as Dynamics users but are flagged in the Payroll_Employee_ID__c custom field for post-migration reference.

  4. Run sample migration with field-level diff

    A representative slice migrates first—typically 100–500 records spanning Accounts, Contacts, Opportunities (Jobs), Work Orders (Cases), and Equipment. We generate a field-level diff comparing Jonas source values against Dynamics destination values for every mapped field, including custom Opportunity fields capturing Jonas job-cost segments. You verify that WIP amounts, budget breakdowns, work-order hours, and equipment serial numbers landed correctly before the full run commits. Any field-mapping corrections are applied to the specification and the sample re-runs.

  5. Full migration with delta-pickup and rollback

    Full migration loads all Jonas Accounts, Contacts, Opportunities with custom job-cost fields, Cases from Work Orders, custom Agreement__c records, Assets from Equipment, and Products from Inventory into Dynamics 365 Sales. A delta-pickup window (typically 24–48 hours) captures any Work Orders or Jobs modified in Jonas during the cutover. FlitStack maintains an audit log of every record created or updated in Dynamics with the corresponding Jonas record ID stored in Source_System_ID__c. If reconciliation fails, one-click rollback reverts all Dynamics changes to the pre-migration state.

  6. Post-migration handoff and rebuild reference

    FlitStack delivers a Migration Handoff Package containing the complete field-mapping spreadsheet, the Jonas Workflow Export documenting every automation rule and J-Mail trigger, the PMA export listing all service agreements and linked equipment, and the Jonas SQL schema diagram used for the export. Your Dynamics admin uses this package to rebuild Jonas automations as Power Automate flows, reconfigure SMTP relay with OAuth 2.0 for J-Mail, and activate Dynamics Field Service scheduling if applicable. We schedule a 30-day post-go-live check-in to verify that delta-sync completed cleanly and that no Jonas records were missed during cutover.

Platform deep dives

Context on both ends of the pair

Jonas Enterprise Service & Construction Software logo

Jonas Enterprise Service & Construction Software

Source

Strengths

  • Job costing with direct GL and payroll posting gives real-time cost visibility per project.
  • Field mobile apps (eMobile, Field Time) capture labor hours from the job site and reduce double data entry.
  • Service dispatch and work order management are integrated with job cost accounting.
  • Document management built in (Jonas Documents, Jonas Forms, J-Mail) centralizes job file storage.
  • Construction-specific payroll handles union rates, certified payroll, and multi-direct deposit for field crews.

Weaknesses

  • On-premise client-server architecture means API access is limited to a legacy SOAP interface with no public bulk export endpoint.
  • Limited third-party integrations — 11 documented integrations versus ServiceTitan's 56 — constrains the ecosystem.
  • G2 reviews cite integration limitations and note the software does not connect to the project management side of construction.
  • Users report the software is not user-friendly, with overcomplicated setup and housekeeping procedures.
  • dated Windows-client interface lacks the modern UX found in SaaS-native construction platforms.
Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

Destination

Strengths

  • Native integration with Microsoft 365, Teams, Outlook, and SharePoint for unified productivity workflow
  • Unlimited custom tables and complex workflows on Enterprise tier enable deep customization for complex sales processes
  • AI-driven predictive analytics and deal intelligence on Enterprise and Premium tiers help sales teams prioritize pipeline
  • Dataverse unified data layer provides a consistent API and data model across all Dynamics 365 and Power Platform apps
  • Strong security model with Field-Level Security and Record Ownership rules for governance-conscious enterprises

Weaknesses

  • Sales Professional tier caps custom tables at 15, creating a migration ceiling for highly customized SMB environments
  • October 2024 pricing increases of $15 per user across all tiers apply to existing customers upon renewal
  • Implementation typically requires costly certified partners, adding 30–50% to total project cost
  • Updates and platform releases can disrupt customizations and plugins, requiring regression testing after each wave
  • Non-Microsoft integrations require additional configuration or middleware, limiting flexibility for heterogeneous tech stacks

Complexity grading

How hard is this migration?

Standard CRM migration. All 8 core objects map 1:1 between Jonas Enterprise Service & Construction Software and Microsoft Dynamics 365 Sales .

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Jonas Enterprise Service & Construction Software and Microsoft Dynamics 365 Sales .

  • Object compatibility

    A

    All 8 core objects map 1:1 between Jonas Enterprise Service & Construction Software and Microsoft Dynamics 365 Sales .

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Jonas Enterprise Service & Construction Software: Not publicly documented.

  • Data volume sensitivity

    B

    Jonas Enterprise Service & Construction Software doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Jonas Enterprise Service & Construction Software to Microsoft Dynamics 365 Sales migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Jonas Enterprise Service & Construction Software to Microsoft Dynamics 365 Sales data migrations

Answers to the questions buyers ask most during Jonas Enterprise Service & Construction Software to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Jonas Enterprise Service & Construction Software to Microsoft Dynamics 365 Sales migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Jonas-to-Dynamics migrations complete in 2–4 weeks of clock time for under 25,000 CRM records. Larger setups with 100,000+ records or Jonas multi-company configurations extend to 6–10 weeks. Jonas on-premise deployments require an additional 3–5 days for SQL schema profiling and DBA coordination before extraction begins. The longest single step is typically the Jonas Job-to-Opportunity field mapping—job-cost segment decomposition into custom Opportunity fields requires your admin to confirm which cost codes map to which custom budget fields before the migration specification is finalized.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Jonas Enterprise Service & Construction Software.
Land in Microsoft Dynamics 365 Sales , intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day