CRM

Migrate your WennSoft data

WennSoft Signature is a Microsoft Dynamics GP–native field service and job-costing suite for skilled trades contractors, with deep equipment and service-call management but limited API access and no native migration tooling.

Encrypted end-to-end with one-click rollback
Talk to a real migration engineer in minutes
WennSoft logo

In its favor

Why people choose WennSoft

The signal that keeps WennSoft on the shortlist. Sourced from G2, Capterra, and customer scoping calls.

Customers running WennSoft are already deep in the Microsoft ERP ecosystem and want purpose-built FSM without leaving Dynamics GP or Business Central, keeping a single vendor relationship for finance and field ops.

The Signature suite covers the full skilled-trades workflow—service calls, job cost, equipment, scheduling, time tracking, and invoicing—under one roof that Capterra reviewers rate 4.7/5.

Companies with large equipment fleets and multi-location customers cite the Equipment Manager module and the Customer-to-Location-to-Equipment hierarchy as reasons they stayed on WennSoft.

MobileTech gives field technicians offline-capable access to service calls and time entry, which reviewers note as a practical advantage for distributed workforces.

Organizations with complex billing structures appreciate the Extended Pricing Matrix for setting billing rates by call type, problem type, and equipment type.

Integration projects take longer than expected with frequent glitches, and Capterra reviewers flag customer support responsiveness as a pain point during implementation and troubleshooting.

The product is described as very inflexible: billing rates cannot be changed once an invoice is posted, and cost-plus job billing amounts have limited adjustability after posting.

The CRM component (Key2Act legacy product) is considered underpowered compared to modern CRMs, pushing sales-focused teams toward Salesforce or HubSpot.

Onboarding new users requires significant training due to the dense, ERP-style UI rather than modern SaaS conventions, increasing total cost of ownership.

Companies outgrowing Dynamics GP as their ERP find the tight WennSoft–GP coupling a liability and migrate the whole stack together to Business Central or a cloud-native FSM.

Reasons to switch

Why people leave WennSoft

The recurring reasons buyers give for replacing WennSoft. Presented as facts, not knocks.

Platform scorecard

Strengths, weaknesses, and where WennSoft fits

Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.

SWOT — strengths, weaknesses, and use-case fit

Strengths

Purpose-built for skilled trades—service calls, job cost, equipment, and scheduling all in one ERP-native suite.Tight integration with Microsoft Dynamics GP and Business Central for finance and accounting continuity.Equipment Manager module provides detailed asset records tied to customer locations and service history.MobileTech gives field technicians offline-capable mobile access to dispatch and time entry.12,000+ skilled trade professionals actively using MobileTech, indicating production-scale field deployment maturity.

Weaknesses

Very limited public API documentation—bulk export requires direct SQL or WennSoft-assisted data pull.Billing rates locked after invoice posting with no retroactive adjustment, creating rigidity in cost-plus billing scenarios.ERP-style UI with a steep learning curve compared to modern cloud FSM products.Customer support responsiveness is cited as a pain point in Capterra reviews, particularly during integration troubleshooting.No native migration tooling; organizations moving off WennSoft must build custom export paths or rely on third-party migration services.

Where it works

Mid-sized skilled trades contractors (HVAC, plumbing, electrical) already running Microsoft Dynamics GP who need purpose-built FSM without abandoning their ERP vendor.Organizations managing complex multi-location customer hierarchies with large equipment fleets, where detailed asset records tied to service history drive recurring revenue.Field service operations with distributed technicians requiring offline-capable mobile access to dispatch tickets, time entry, and customer equipment records.Service businesses with complex billing structures that require extended pricing matrices calculating rates by call type, problem type, and equipment type.Companies prioritizing finance-and-field accounting continuity, where invoicing, job costing, and time tracking must live within the same Microsoft ERP ledger.

Where it struggles

Organizations requiring frequent billing adjustments or retroactive invoice corrections, since billing rates become locked after posting with no retroactive adjustment.Companies with strong sales-focused CRM needs, as the legacy Key2Act CRM component is considered underpowered compared to Salesforce or HubSpot.Businesses planning to migrate off WennSoft, since bulk export requires direct SQL access or WennSoft-assisted pulls with no native migration tooling available.Teams expecting a modern cloud-native UX with minimal onboarding friction, given the dense ERP-style interface requiring significant user training.Organizations needing rapid integration with modern third-party tools, where integration projects frequently encounter glitches and extended timelines.

Pricing tiers

WennSoft pricing overview

WennSoft publishes a starting price of $100/user/month on Capterra for the Signature Core tier. Upper tiers (Plus, FORGE) and enterprise agreements are not publicly listed and require a sales conversation. The Capterra listing reflects a 4.7/5 rating from 93 reviews.

Signature Core

Tier 1 of 3

$100/user/month

What's included

Service Management and Job Cost moduleEquipment ManagementScheduling and dispatchTime and Expense ManagementMobileTech field mobility app

Need help selecting your CRM?

Book a free 30 minute consultation

Pricing is informational. FlitStack AI does not bill on WennSoft's schedule — see our quote-based pricing →

What gets migrated

WennSoft object support

Object-by-object support for WennSoft migrations. Per-pair details surface during scoping.

Customers

Fully supported

Customers is the top-level entity in WennSoft's hierarchy. Each Customer can have multiple Locations, and the Location holds Equipment and Contacts. We export the full Customer list with address and contact relationships intact.

Locations

Fully supported

Locations are child records of Customers. The Location pane in WennSoft exposes Equipment and Contacts tabs per location. We map each Location to its parent Customer ID and preserve the site-level address data.

Equipment

Fully supported

Equipment Manager is a dedicated WennSoft module storing detailed asset records linked to Locations and Customers. We export the full equipment hierarchy including make, model, serial number, and service history.

Service Calls

Fully supported

Service Calls are the core work record in WennSoft, tied to a Location and optionally to Equipment. We export call status, problem type, call type, labor lines, and materials used. Unbilled calls (call status other than Complete) are flagged separately.

TimeTrack / Labor Records

Mapping required

TimeTrack data can be exported to third-party payroll modules via a field-mapping workflow. We sequence TimeTrack records by employee, date, and billable flag, and map them to the destination's time-entry or payroll object. Non-billable time entries may require explicit handling.

Job Costs

Mapping required

Job costs in WennSoft accumulate from labor, materials, and subcontractor lines tied to a Service Call. The Unposted Costs column in the Job Status window tracks amounts not yet invoiced. We chunk job costs by status (posted vs. unposted) and map them to the destination's project-cost or work-order cost record.

Unbilled Costs

Mapping required

The Unbilled Costs report specifically lists labor costs for unposted service calls with status other than Complete. We extract this report separately and map it as open billing items in the destination system rather than as historical records.

Extended Pricing Matrix

Mapping required

The Extended Pricing Matrix defines billing amounts and markups by call type, problem type, equipment type, and other criteria. These are lookup rules, not transactional records. We map the active matrix rows to the destination's pricing-rules or billing-rate objects, noting that not all destinations support criteria-based pricing logic.

Service Invoicing / Billing Records

Mapping required

Service invoicing in WennSoft defaults labor to billing rates and accumulates costs before invoicing. We export posted invoice history as financial records. Because billing rates cannot be retroactively changed after posting, we preserve the locked amounts as-is.

Contacts

Mapping required

Contacts are associated with either a Customer or a Location within a Customer. The Contact-to-Location relationship must be preserved during mapping since some destinations conflate Contacts with site-level persons.

Inventory Items

Fully supported

Inventory items track parts and materials used on service calls. We export item number, description, unit cost, and on-hand quantity, mapping to the destination's inventory or materials object.

Users / Technicians

Mapping required

Users in WennSoft include office staff and field technicians assigned to dispatch. We map user records to the destination's employee or technician object, preserving scheduling assignments. Role-based access (technician vs. admin) is mapped as a custom property where the destination lacks an equivalent role model.

Scheduling / Dispatch

Mapping required

Scheduling in WennSoft assigns technicians to service calls with appointment dates. We export dispatch records as work-order assignments in the destination. Scheduling rules, multi-day routes, and geographic dispatch logic require custom mapping since destination platforms use different optimization models.

Gotchas

What to watch for in WennSoft migrations

Issues we've hit on past WennSoft migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.

High

Invoice posting locks billing rates permanently

High

Unposted Costs and Unbilled Costs require separate extraction

Medium

Integration complexity and frequent glitches slow migrations

Medium

No public bulk export API documented

Low

Dynamics GP edition gating may block migration paths

How a WennSoft migration works

Four steps, WennSoft-specific

Connect

Not publicly documented into WennSoft. Scopes limited to read-only on the data we move.

Map

We translate WennSoft-specific structures (custom fields, objects, value lists) to the destination's model.

Sample

Test with a 50–200 record subset to validate WennSoft quirks before production.

Migrate

Full migration with WennSoft rate-limit handling. Rollback available throughout.

FAQ

WennSoft migration FAQ

Answers to the questions buyers ask most during WennSoft migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your WennSoft migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most WennSoft migrations under 1M records finish in 48–72 hours end-to-end. Larger orgs with custom objects or buyer-side security review typically take 5–7 days.

Ready when you are

Migrate WennSoft.
Without the rebuild.

Free scoping call with a migration engineer. Tell us about your WennSoft setup and destination — written quote back within a business day.

Free scoping call Quote in 1 business day 1,784 platforms supported