Why java.util.Date Is Deprecated and How to Migrate to the java.time API

Java's original java.util.Date class suffers from many design problems: a misleading name, mutability, non‑finality, reliance on the system time‑zone, zero‑based month indexing, a 1900‑based year, ambiguous method names, and unclear handling of leap seconds and tolerant ranges.

Because of these issues, most of its functionality was deprecated in Java 1.1, and modern code should avoid using Date and its subclass java.sql.Date .

The migration is driven by code‑quality rules that flag Date usage as a defect. The recommended replacement is the java.time package introduced in Java 8.

How to migrate

1. Identify the purpose of each Date field (date‑time, date only, time only, or timestamp) and choose the appropriate java.time type:

LocalDateTime for date and time without a zone.

LocalDate for date only.

LocalTime for time only.

Instant or ZonedDateTime for timestamps with zone information.

2. Update data‑object classes, replacing Date fields with the selected java.time types.

Code examples

Replace old date creation:

Date nowDate = new Date();
Date nowCalendarDate = Calendar.getInstance().getTime();

With the new API:

// Instant represents a point in time (similar to Date)
Instant nowInstant = Instant.now();
// LocalDateTime for date‑time without zone
LocalDateTime nowLocalDateTime = LocalDateTime.now();
// ZonedDateTime for date‑time with zone
ZonedDateTime nowZonedDateTime = ZonedDateTime.now();
// Convert back to java.util.Date if needed
Date nowFromDateInstant = Date.from(nowInstant);
// Convert to java.sql.Timestamp
java.sql.Timestamp nowFromInstant = java.sql.Timestamp.from(nowInstant);

Refactor utility methods, for example:

public static String dateFormat(LocalDateTime date, String pattern) {
DateTimeFormatter formatter = DateTimeFormatter.ofPattern(pattern);
return date.format(formatter);
}

And arithmetic methods become concise:

public static LocalDateTime addSecond(LocalDateTime date, int second) {
return date.plusSeconds(second);
}
public static LocalDateTime addMinute(LocalDateTime date, int minute) {
return date.plusMinutes(minute);
}
// similarly for addHour, addDay, addMonth, addYear

Other conversions, such as getting the day of week, start/end of day, and range checks, are also simplified using java.time methods.

Conclusion

While the migration can be extensive—affecting DO entities, converters, and DTOs—it eliminates fragile code, reduces bugs caused by mutable dates, and aligns the project with modern Java best practices.