Certified Professional Controller; CPC; at Denver TRACON (Pueblo Sector); reported a recurring automation failure between D01 (PUB Sector); and Springs departure; COS. Automation handoffs received; do not transfer necessary aircraft data to provide required service. Further interfacility automated handoffs to Denver ARTCC; ZDV; do not display and transfer correct data.

Narrative

Took over PUB (Pueblo) sector and COS (Colorado Springs) called for a handoff on Aircraft X. I accepted the handoff - datablock was indicating VFR; and like normal - displayed no type aircraft or destination. I didn't have a strip on the aircraft; so assumed aircraft was on a local code - because the data block appeared to be a local code since it was void of any information.When the pilot checked in; I asked his type aircraft and destination. Pilot responded with 'DHT'. I then inquired if pilot wanted flight following all the way to DHT. Pilot replied; 'We have an IFR on file'. I said oh; you have one on file? And pilot instructed me he was currently IFR at 10000 and had already received IFR clearance after departure. I called COS to ask if the aircraft was IFR and they said YES. Aircraft was on the IFR code that was in the NAS (National Airspace System) after I had flight data look for information on him. There was no strip at the PUB sector or in the strip basket next to PUB. Since the code was correct; the aircraft should have been able to be handed off to ZDV without issue since flight plan was IFR in the NAS. However; when I initiated a handoff to ZDV; it flashed 'Local Flight plan'. So; I had flight data remove the flight plan and put a new one in so that the automation would work correctly down the road. This is a HUGE problem with the automation between COS and PUB. No one seems to have any answers but this automation issue has been happening for months. It is UNSAFE; and NEEDS TO BE FIXED IMMEDIATELY. We can't possibly work traffic when one controller thinks an aircraft is IFR; the pilot thinks he is IFR; but the next controller takes the handoff; has ZERO information on the flight plan; and the datablock is indicating VFR. This is DANGEROUS.