Importing Client Asset Data Into QuickBooks Fixed Asset Manager
Users bringing outside asset records into Fixed Asset Manager must map five required fields before the import will succeed, or risk missing or misclassified depreciation data.
Importing asset records from an outside client file into QuickBooks Fixed Asset Manager is not a simple open-and-go process. Before any data moves over, users have to build a mapping template that tells Fixed Asset Manager how each field in the source file corresponds to the fields it expects — and if that template is incomplete or mismatched, the import can produce assets with missing depreciation methods, incorrect recovery periods, or basis values that do not line up across federal, AMT, ACE, book, or state columns.
What Mapping Actually Means
Mapping is the step where a field in the source depreciation file — say, one labeled “Date Placed in Service” — gets matched to the equivalent field in Fixed Asset Manager, such as “Date Acquired.” The mapping is saved as a reusable import template, so an accountant who imports client files regularly only needs to set it up once and can apply it to subsequent imports.
The concept sounds straightforward, but the friction arises because different depreciation programs handle asset classification differently. Some programs rely on statutory asset types — Real Property, Luxury Automobile, Listed Property, and so on — to determine the required federal depreciation method. Fixed Asset Manager takes a different approach: it folds those statutory asset types into its own federal depreciation method definitions rather than treating them as a standalone classification field. Users who expect a one-to-one field match can be caught off guard by that structural difference.
The Five Fields That Must Be Mapped
Fixed Asset Manager requires five source fields to be mapped before an import will work correctly:
- Asset Description
- Date Acquired
- Cost
- Method
- Life
If any of these are left unmapped, the import will not populate the asset records the way the user expects. These are the minimum data points Fixed Asset Manager needs to calculate depreciation going forward.
What Happens to Unmapped Bases
Many Fixed Asset Manager client files carry multiple basis tracks beyond federal — AMT, ACE, Book, State, and Other. If those bases exist in the client file but the user has not mapped them in the import template, Fixed Asset Manager applies a set of fallback rules rather than leaving the fields blank:
- Date Acquired and Cost for the unmapped bases default to the federal values.
- Method defaults to whatever the import template specifies as the default method.
In other words, unmapped bases do not disappear — they inherit federal cost and acquisition date and pick up a generic method. That may or may not be correct for a given asset, so users importing files with multiple basis tracks should review those records after import rather than assuming the defaults are right.
Fixed Asset Manager also handles some calculations automatically during the import. For ACRS and MACRS assets, it computes the Section 179 deduction from the federal basis and disables salvage value, consistent with how those asset systems work. It selects AMT and ACE recovery periods on its own if those periods were not mapped in the template.
Fields With ID-and-Description Mapping
Fixed Asset Manager gives users the ability to map both an ID and a description for several supporting fields:
- Category
- Location
- Vendor
- Amortization
- User Defined 1 through 5
There is a catch worth noting: even though both the ID and the description can be mapped, only the description actually comes through on import. Users who rely on the ID field for internal tracking or cross-referencing will find that it does not populate after the import completes.
Practical Takeaway
The accepted guidance is to treat the import template as the single most important part of bringing outside asset data into Fixed Asset Manager. Getting the five required fields mapped correctly is the baseline; reviewing how AMT, ACE, Book, State, and Other bases were handled — and confirming that default methods applied to unmapped bases are appropriate — is where most of the post-import cleanup tends to happen.
For users dealing with broader company file conversion or downgrade issues alongside the Fixed Asset Manager import, the mapping template is still the right place to start, since it isolates the asset-data transfer from the rest of the file migration.