A: Yes. Binti documents, often referred to as unstructured data, are planned to be migrated into CWS-CARES.

A: Yes. CWS/CMS is the system of record. If a field already exists in CWS/CMS, Binti data will not override it.

A: Yes. Client IDs are essential for forming the correct relationships during conversion. The Project will share which counties have missing Client IDs.

A: If counties are in need of CWDS Website log-in support, please contact Customer Relations.

A: The approved Binti modules for CWS-CARES data conversion are as listed below:

• Resource Family Approvals (RFA)
• Placement
• Family Finding

A: Data mapping sessions determine what does or does not have a place in CWS-CARES.

Most Binti data aligns with CWS-CARES and converts successfully. County-specific or Binti-specific fields are reviewed during mapping, including:

• Administrative fields
• County-specific process fields
• Binti administrative/technical fields
• Data with no CWS-CARES equivalent

A: In the event that data doesn't match or cannot be converted when migrating to CWS-CARES from Binti, there are two steps:

1. Project will share the list of data elements that cannot be moved into CWS-CARES through the conversion process. This includes data with incorrect data types, incorrect picklist values or missing mandatory data element information. If Binti provided information is different from CWS/CMS information, then Binti provided data will be rejected and shared with Counties.
2. Counties validate the data. If an issue is found, it becomes a ticket. The Project investigates, fixes the issue, redeploys the data, and counties revalidate.

A: Yes, there are certain activities that counties should practice when validating converted data. As guidance, counties should practice the following:

• Identify knowledgeable staff
• Validate accuracy and completeness
• Run county-specific test scenarios
• Provide structured feedback