Migrating from AutoCAD Electrical: A Practical Checklist

What actually transfers

Files move. Meaning does not, unless you rebuild it.

The pattern is consistent: anything that was a drawing survives as a drawing, and anything that was data has to be re-entered as data. Budget the second category, not the first.

What does not come across at all

Be explicit with your team before the pilot, because this is where expectations break:

• PLC and control schematics. Not supported by light building-electrical tools, including GorkyCAD. Keep a platform for that work.
• True DWG editing. DXF import and export, not a DWG editor. Dynamic blocks, attributes and external references will not round-trip.
• Offline work. A browser tool needs a connection. Site visits without signal are read-only.
• Automatic wire numbering on machine drawings. The rule engine that makes AutoCAD Electrical valuable for panel wiring does not have an equivalent here.
• Your old libraries as libraries. Symbols become placeable objects, not a curated catalogue with a maintainer.

If two or more of those are core to your revenue, stop here. The rest of this article is for teams where they are peripheral.

Phase 1: inventory before you touch anything

Spend a week writing down what you have. This is the step teams skip and regret.

1. List active projects and their drawing sets. Separate "will be revised" from "archive only".
2. Count deliverable types — layout, single-line, panel schedule, cable schedule, calculations, BOM. For each, note who consumes it.
3. Name the conventions. Layer naming, tag format, device numbering, title block fields. Write them down; they are the real specification for the new tool.
4. Identify the human dependency. Who knows how the templates work? What happens when they are on holiday?
5. Record the handover format. If a client contractually requires DWG with attributes, that contract is a constraint, not a preference.

Output: one page, shared with the team. Without it, the pilot has no success criterion.

Phase 2: pilot on a finished project

Pick a project that is complete, typical, and was successful. Not the most complex one, and not a new one where you cannot compare against a known result.

• Import the plan as DXF or PDF and check the geometry against the original.
• Rebuild devices and circuits. Time it honestly, including the corrections.
• Generate the panel schedule and the single-line diagram.
• Export PDF, DXF, XLSX and compare with the original set, line by line.
• Record the delta: what is missing, what is better, how many hours it took.

This is the only reliable way to price the switch. A demo takes twenty minutes; a pilot on a real project takes a day and tells you the truth. You can start from the demo and then repeat it on your own file.

Phase 3: run in parallel, not instead

For the first two or three live projects, produce the new set alongside the old one. It costs time and it is worth it:

• The old set protects the deadline.
• The new set exposes problems while a fallback exists.
• The comparison gives you a defensible answer when someone asks whether the change was worth it.

Do not announce the migration to clients during this phase. Deliverables should look the same; the internal route is your business.

Phase 4: cut over by project type, not by date

A single cut-over date creates a cliff. Cut over by deliverable class instead:

1. New residential projects first — small sets, fast feedback.
2. Then small commercial.
3. Then anything with unusual approval requirements, last.

Archive projects stay in the old system permanently. Reopening a 2018 project in a new tool is almost never worth the rebuild; export it to PDF and keep the source.

Phase 5: close the loop

• Retire the old licences only when no active project depends on them.
• Write a one-page "how we do it now" note: layer mapping, tag format, export presets.
• Assign an owner for the conventions. Without an owner, they drift.
• Keep one machine able to open old files, even if only for reference.

A realistic timeline for a small team

Small teams move faster than this; teams with a single expert and no documentation move slower. The pilot week is not compressible.

Risks and how to contain them

The one expert leaves. The inventory page is the mitigation. Write it before you need it.

A client demands DWG with attributes. Identify these clients in phase 1 and keep a route for them. Do not discover it at handover.

Quality dips during parallel running. Parallel work doubles the load for a few weeks. Schedule it against a quiet period, not against a tender deadline.

Conventions drift. Two people invent two tag formats within a month. Publish the convention and check it in review.

Over-promising on automation. The 41 built-in checks catch rule-based errors; they are not a certification and they do not replace engineering review. Teams that treat them as a signature ship mistakes with confidence.

Underestimating rework on old projects. A revision request on a 2019 project can consume a day. Price that in, or decline it.

When not to migrate

Stay with AutoCAD Electrical if your revenue depends on machine or panel wiring documentation, if DWG with attributes is a contractual deliverable, if you need offline operation, or if your library is a genuine competitive asset maintained by a person who is still there. The tool is not the problem in those cases; it is doing a job the alternatives do not do.

Migrate if your work is building electrical, if your team is small, if licences and Windows machines are a recurring cost, and if the bottleneck is drafting hours rather than engineering depth. The full comparison of alternatives is in the buyer's guide and the seven-tool comparison.

If you are evaluating GorkyCAD specifically, read the pricing page for current plans and the documentation for export formats and limits before the pilot, not after. The free tier — 3 projects, 100 objects — is enough to run phase 2 on a real project.

Sources

• Autodesk, AutoCAD Electrical toolset — autodesk.com
• Autodesk, DXF reference documentation — help.autodesk.com
• EPLAN Electric P8 (comparison baseline) — eplan.com
• IEC 60364 series, low-voltage electrical installations — webstore.iec.ch
• NFPA 70, National Electrical Code — nfpa.org

Informational only, not legal or engineering advice. Licence terms and export capabilities change; verify current vendor documentation, and check deliverables against the contract and the code edition in force for each project.