I have figured out how to do it. It is not easy but it is worth it to get a good layout. I will name the net when laying out the PCB and then go back to the schematic and add that net with that name. I don't know if I will be able to later update the PCB with the schematic changes.

Try it. It is not good to change PCB, you would better to change schematic, then import to PCB.

> It is not good to change PCB, you would better to change schematic, then import to PCB. I guess I can do that. I'll have to figure out a few net assignments, go back and change the schematic, import it, place the net and then do that over and over. I have 100 pins that I am going to route this way.

Yes, you can.

@Mchahn, I have done a similar thing in the past. For some very arcane reasons I had a huge LTspice schematic with over 1000 connector pins - the connectivity of which had all been verified in simulation - that I then needed to turn into a non-simulation schematic suitable for porting to the PCB layout tool of Vutrax. Having produced a verified schematic, I decided not to redraw the schematic in Vutrax to avoid the chance of making any mistakes. I also needed to be able to show the person doing the PCB layout exactly how I wanted the layout to be done. The way I approached it was to create the relevant symbols in the LTspice and then draw the schematic as if it were a PCB layout. I placed the connectors and other components in the same relative positions that they would be on the PCB and then routed the schematic nets to show how they were to be laid out on a multilayer PCB. Nets on each layer were enclosed in ellipses and annotated to help identify them and they were drawn to minimise crossings (and so avoid changes from one layer to another). * If you give schematic nets names that also include a layer designation that will be a big help when it comes to PCB layout. If you use this approach in EasyEDA then when you convert the schematic to PCB, as you start routing you already know which layers sets of rats have to be routed on and you also know that they can be routed without having to worry too much about them crossing over. All this will all be much, much easier in EasyEDA because in my case there is no tool to directly convert an LTspice netlist to a Vutrax format so I had to make my own... :)