Built-In PDM or Custom Development? Drawing Output and Migration Decisions

Eligibility: valid existing licenses and expired or independently non-renewed maintenance

SOLIDWORKS PDM work is assessed only for customers with valid, lawfully held existing licenses whose maintenance has expired, or customers who independently decide not to renew and plan implementation after maintenance ends. Each case requires review of licenses, existing contracts, third-party access, API/SDK rights and migration conditions. Expired maintenance does not establish license validity or permission for development or migration.

Non-renewal is the customer's independent decision. This article does not recommend terminating contracts or position engineering as a replacement for vendor maintenance. Preliminary scoping may occur earlier, but implementation under this offer requires maintenance to have ended and case-specific rights to be confirmed.

Case-by-case review before work

• Verify license type, validity, entitled version, entity and devices for PDM, CAD, SQL, Task Hosts and dependencies. Do not implement using expired term licenses.
• Review applicable vendor, reseller, maintenance and other contracts for third-party access, confidentiality, IP, development and relocation limits. Obtain legal review or vendor confirmation when needed.
• Confirm authority to commission work and supply data, code, installation media and access. Do not use another party's accounts, keys or restricted support resources.
• Check API/SDK, Document Manager and dependency licenses and access eligibility. Public API documentation is not itself a development or distribution license.
• Assess backups, isolated rehearsal, compatibility, downtime, rollback and acceptance before agreeing scope in writing. Unclear rights or unmet conditions prevent acceptance.

Potential scope and exclusions

After prerequisites are met, assess configuration, integration, approved-API customization, batch output and relocation within the lawfully licensed existing version. Capability, rights and tests determine each deliverable; this is not an unconditional promise.

AxiomX provides independent third-party engineering, not vendor- or reseller-authorized maintenance, dealership or agency services under this offer. Vendor maintenance, renewal, new releases, licensing and activation rights must be confirmed through the vendor or a legally authorized channel.

• Do not provide or promise maintenance renewal, new releases/service packs/media, license sales/transfers/reactivation or vendor defect-fix entitlements. Required rights must be handled through lawful channels.
• No activation/license bypass, impermissible commercial use of trial/education/third-party licenses, unauthorized vendor-code modification or reverse engineering.
• No guarantee that old versions run on every new OS or support every format/API. Newer documentation does not grant an upgrade entitlement.
• Engineering does not automatically preserve, restore or extend vendor warranty, maintenance or other rights; assess effects before work.

References and contractual boundaries

Product names identify existing customer systems and documentation; trademarks and vendor rights remain with their owners. Links are technical references, not vendor authorization, partnership, endorsement or case approval.

This is not legal advice or a guarantee of permissibility under every contract. Applicable agreements and license terms control. Website notices and customer declarations cannot override third-party rights or replace necessary legal review.

Assess SOLIDWORKS PDM before custom development

Standard and Professional task capabilities are not interchangeable. Standard documents workflow Drawing to PDF; Professional Convert documents additional output, configuration/sheet and naming settings. Verify the installed edition, version and samples. Autodesk Vault references apply to that other platform, not SOLIDWORKS PDM procedures.

• Inventory edition, service pack, SOLIDWORKS and Task Host versions and licensing.
• Separate feature gaps from configuration, data and operating issues.
• Test native output before estimating custom work.

When configuration is enough

• Existing lifecycle, access, cards and numbering meet requirements.
• Supported selection, formats, sheets and naming satisfy delivery.
• Queues and exceptions pass agreed tests.
• Vendor-supported configuration can reduce some compatibility burden but still needs testing.

When customization merits assessment

• Special BOM, effective-revision or cross-project selection.
• Supplier packages, custom naming, delivery locations or system write-back.
• Additional validation, retries, audit or integration.
• Confirmed gaps with agreed APIs, licenses, support and ownership.

Include custom-deliverable upkeep (not vendor maintenance)

• Specify versions, APIs, dependencies and service accounts.
• Agree tests, bug-fix scope, compatibility and change requests.
• Confirm source code, usage rights, deployment and handover in the contract.
• Compare development, licenses, testing and future upgrades.

Combine migration and upgrade?

Upgrade, media and activation rights must first be obtained through lawful channels; this independent service does not grant them. Once rights are confirmed, combining may reduce outage events but increases troubleshooting and rollback variables.

• Separate when same-version operation can be proven first.
• Consider combining if the old version cannot support the target environment and rehearsal proves recovery.
• Check database, vault, CAD, custom code, licensing and interfaces in both cases.
• Decide using measured rehearsal, acceptance and outage limits.

Request evidence before purchase

• Native/custom gap list and acceptance criteria.
• Versions, licenses, interfaces and limits.
• Real drawings and role-based tests.
• Cutover, rollback, documentation, ownership and exclusions.