Migration guide
WCF contracts are already formal, which makes them a good starting point and a trap: the serializer adds behavior the attributes do not show. This guide covers both and the workflow to a reviewed OpenAPI document.
By Pranav Kulkarni, Head of Language Engineering · Updated 15 Oct 2026
Technical syntax challenges
[DataMember(IsRequired = true)] requires the element to be present, but a reference type can still be sent as nil. In JSON Schema that is a required property whose type includes null, unless the service code rejects nulls, which the extractor checks.
A DateTime or decimal DataMember that is not required and not sent deserializes to DateTime.MinValue or 0. Business logic downstream may treat 0001-01-01 as 'no date'. That convention must become an explicit optional field.
Name = "LossDt" changes the wire name, Order fixes element order in XML, and EmitDefaultValue = false omits default values from responses. Clients written against the wire format depend on all three, so the schema uses wire names and documents omission.
[KnownType(typeof(AutoClaim))] lets a base-typed member carry subclasses, signaled by xsi:type in XML or __type in WCF JSON. In OpenAPI this becomes oneOf with a discriminator property, which needs a name the business agrees on.
[FaultContract(typeof(PolicyNotFoundFault))] defines typed errors that map to HTTP statuses with problem details bodies. IsOneWay = true operations return nothing and map to 202 Accepted with an asynchronous follow-up.
wsHttpBinding with message security, reliable sessions or transactions flowing over WS-AtomicTransaction carry guarantees that plain HTTP does not. The spec lists which operations relied on them so the REST design can provide equivalents.
Extraction workflow
The sequence a PYD ENTERPRISES Discovery Scan runs for this stack. Every output links back to source file and line range.
Provide service and contract assemblies or source, web.config or app.config with bindings and behaviors, and any published WSDL and XSD for cross-checking.
PYD ENTERPRISES reads ServiceContract, OperationContract, DataContract, DataMember, EnumMember, KnownType and FaultContract attributes and the serializer each endpoint uses.
Service methods are parsed to find null checks, default-value conventions and validation that tighten or loosen what the contract attributes say.
Security mode, sessions, transaction flow and one-way operations are recorded per endpoint as non-functional requirements.
Operations, schemas with wire names, oneOf polymorphism and fault-derived error responses are exported, each with source links.
Fixtures with the old wire format and the new JSON are generated so both endpoints can be tested side by side during migration.
Legacy in, specification out
Left: the WCF construct as it sits in production. Right: the reviewed artifact your REST / OpenAPI 3.1 engineers build against. PYD ENTERPRISES produces the spec and the tests; your team writes the service.
LEGACY SOURCE
1[ServiceContract]2public interface IClaimService3{4 [OperationContract]5 [FaultContract(typeof(PolicyNotFoundFault))]6 ClaimResult SubmitClaim(ClaimRequest request);7}89[DataContract(Namespace = "http://schemas.example.org/claims/2014")]10[KnownType(typeof(AutoClaim))]11[KnownType(typeof(PropertyClaim))]12public class ClaimRequest13{14 [DataMember(IsRequired = true, Order = 1)]15 public string PolicyNumber { get; set; }1617 [DataMember(IsRequired = true, Order = 2)]18 public decimal LossAmount { get; set; }1920 [DataMember(Name = "LossDt", Order = 3)]21 public DateTime LossDate { get; set; }2223 [DataMember(EmitDefaultValue = false)]24 public string AdjusterCode { get; set; }25}
EXTRACTED ARTIFACT
1{2 "$schema": "https://json-schema.org/draft/2020-12/schema",3 "$id": "urn:claims:2014:ClaimRequest",4 "title": "ClaimRequest",5 "type": "object",6 "required": ["claimType", "PolicyNumber", "LossAmount"],7 "properties": {8 "claimType": { "enum": ["AutoClaim", "PropertyClaim"] },9 "PolicyNumber": { "type": ["string", "null"] },10 "LossAmount": { "type": "number" },11 "LossDt": {12 "type": "string",13 "format": "date-time",14 "$comment": "absent = DateTime.MinValue in WCF; 3 callers test for it"15 },16 "AdjusterCode": { "type": "string" }17 },18 "x-pyd-source": "IClaimService.cs:9-27",19 "x-pyd-faults": { "PolicyNotFoundFault": 404 }20}
Architectural best practices
In depth
It is tempting to export the WSDL, run a converter and call the result an OpenAPI document. That gives you structure, not behavior. The WSDL does not tell you that PolicyNumber can be null on the wire, that three callers treat a missing date as 'unknown' through DateTime.MinValue, or that the service implementation rejects loss amounts above a threshold. Those come from the code.
PYD ENTERPRISES reads contracts, configuration and implementation together and exports an OpenAPI 3.1 document and JSON Schemas that reflect what the service really accepts and returns, with source links. Your team builds the REST service; PYD ENTERPRISES does not generate it.
WCF services often implement IExtensibleDataObject so unknown members round-trip without loss, which let old and new clients coexist. A REST replacement needs an equivalent policy: additionalProperties behavior in the schema, a versioning scheme in the path or media type, and a rule for how long old fields are accepted. The extracted spec records which DataContracts were extensible and which fields were added later (from Order gaps and namespace changes), which gives architects the evidence to choose that policy.
FAQ
Yes. Services marked with XmlSerializerFormat are analyzed with XmlSerializer rules, including XmlElement and XmlAttribute attributes, which change names and optionality differently.
A WSDL and XSD import gives contract structure. Without service code, the behavior-dependent parts such as null handling and default conventions are flagged as unverified in the review queue.
Callback contracts and streamed operations are recorded and flagged; they usually map to AsyncAPI 2.6 event channels or chunked endpoints, which architects decide during review.
Request a codebase scan and review extracted rules, contracts and fixtures for your own WCF estate, inside your VPC.