The Contact Import Staging object/page has fields where Middle Name and Suffix can be captured and a flow that will map them to the contact object. However, your org may not use those fields or want that functionality. Make adjustments to the Name Settings as instructed below then make edits to the flow based on your org's settings.
Adjust Name Settings to not use/use middle name and suffix
Click Setup, Search and Select User Interface
Scroll to User Interface and click it
Scroll to Name Settings and check/uncheck the appropriate box to use or not use middle name and suffix
Save
Now the flow needs a few adjustments
Select Setup>Search and Select Flow then search for the flow labeled FdnpContactImport
If flow is Active, Deactivate
Click Save as New Flow and give it a new name, such as FdnpContactImport2
To fix issues in new flow
Click Toolbox icon in upper left
In the fmlPreferredPhone formula, replace the {!$Record.HomePhone_c} and {!$Record.CellPhone_c} with the fields that start with fdnp_cf1_
In the fmlProcessingNotes formula, replace the {!$Record.ExtSysId_c} with the field that starts with fdnp_cf1_ and replace the {!GetContact.ExtSysId_c} with the {!GetContact.fdnp_cf1_ExtSysId_c}
Formula should read: IF({!varNewContactFlag}, 'New contact created.',IF({!$Record.fdnp_cf1_ExtSysId_c} = {!GetContact.fdnp_cf1_ExtSysId_c},'Contact record updated using external id ' + {!$Record.fdnp_cf1_ExtSysId_c},'Contact record updated using first name, last name and email'))
In the Canvas, select SetNewContact Assignment element
Optional. Consider adding to the Description. Example: Copied from FdnpContactImport. Fixed post=install namespace issues and removed MiddleName/Suffix references since the name settings are not active in this org.