Upgraded to Kicad 4.0.1 . cvpcb not reading old net file?

I want to continue working on a project that up until upgrading to Kicad 4.0.1 (Mac version) was running under Windows (within a parallels VM on my Mac). The Windows version was (2013-07-07 BZR 4022)-stable.

The schematic and layout opened without a hitch.

cvpcb opened with the parts listed. However, each part no longer had its footprint associated with it.

i could be wrong, but if cvpcb reads the .cmp file … the .cmp file exists. Here is an example of an entry:
TimeStamp = /55BE2CDA/55BE2DD0;
Reference = C1;
ValeurCmp = 1u;
IdModule = SM0805;

so i assume it read this because the reference (e.g.: C1) shows…but the associated footprint (SM0805) is not assigned within cvpcb.

does this mean modules used in the previous stable version from 2013 are not available for the transition? If this is the case, doesn’t this mean I have to redo my (entire) layout - which would be a major time sync not to mention i’ll inevitably introduce errors.

shouldn’t i be able to use the old footprint and association in kicad 4.0.1?

Thank you.

module libraries got changed from the 2013-stable when pcbnew was refurbished - same fate eeschema will have to go through.
Back then several modules where in a single library file vs now each module is it’s own file in a folder… format must have changed as well.

You have to locate the old legacy footprint libraries you have been using and load them via the library manager.
There is an option in the library manager for each library (Plugin Type) that needs to be set to legacy to load the old footprints.

Others with more knowledge will surely chime in with more detailed info or links.

I recently migrated a small project from 4022 to 4.0.0, it took a while but I was not familiar with the new concepts in the v4 Kicad and wanted to get a grip on the details. I think I have now got a good idea, and to be honest the Kicad devs and library maintainers have done a pretty good job with the new features, they are good step forward (apart from a few bear traps…!).

However, the new v4 is different in critical places, and there is very limited automatic migration provided in Kicad. I haven’t written down the process I followed, but since then I found a pretty good guide on the web https://rheingoldheavy.com/new-stable-kicad-10-steps-to-import-an-old-kicad-project/

Thank you. the article was helpful in validating i can’t use the old standard libraries during transition. it helps a lot to have a better idea of what is going on.