Hi Mike,
There isn't a specific procedure for Parcel Fabrics versus any other complex geodatabase object. Make sure you have a clear understanding of the requirements needed. There are a few things I would make sure to check and go over before making the transition. You can simply copy and paste the feature dataset from the File Geodatabase into the Enterprise Geodatabase.
1) Make sure you know what geometry storage type you want to use. 10.3.1 Defaults are ST_Geometry for Oracle and Geometry for SQL Server
Feature classes in a geodatabase in SQL Server—Help | ArcGIS for Desktop
Feature classes in a geodatabase in Oracle—Help | ArcGIS for Desktop
2) Understand the versioning structure with Parcel Fabric editing. Parcel Fabric editing only supports child versions off of the Default version. Grandchild versions are not supported for Parcel Fabric editing.
Also important, Parcel fabric versions and edit locking found in the documentation below.
Editing the parcel fabric and versioning—Help | ArcGIS for Desktop
3) Just like any other large data format in an Enterprise Geodatabase, it is crucial you stay on top of reconciling/posting versions, compressing the geodatabase, rebuilding indexes, and analyzing datasets.
Geodatabase maintenance—Help | ArcGIS for Desktop
http://desktop.arcgis.com/en/arcmap/10.3/manage-data/gdbs-in-sql-server/geodatabase-version-administ...
That is a lot of documentation, but feel free to post any questions here and we can get a discussion going. Hopefully that helps out.
Sam
Senior Geodatabase Support Analyst
ESRI